How do I try out/exercise the confidentiality policy intent for the Axis2 WS binding ?
• First you must ensure that you are not encumbered by the legal and licensing requirements of bouncycastle. There are algorithms in the bouncycastle distributions (such as IDEA) that have patent obligations and you are responsible for sorting this out for yourself. • Next you must be familiar with setting up Axis2 for confidentiality. Here are some useful links for this http://wso2.org/library/234, http://wso2.org/library/174, http://wso2.org/library/255. • The itest in the ws-binding-axis2 module and the helloworld-ws-service-secure have definitions.xml file that define the intents and policyset for confidentiality. Change the values that have been provided in the Axis2ConfigParam policy attachment, to suit what you have defined for your application – such as the keystore, the userid and password to the keystore, the password callback handler class etc. • Now, specify the confidentiality intent on any of the binding.
• First you must ensure that you are not encumbered by the legal and licensing requirements of bouncycastle. There are algorithms in the bouncycastle distributions (such as IDEA) that have patent obligations and you are responsible for sorting this out for yourself. • Next you must be familiar with setting up Axis2 for confidentiality. Here are some useful links for this http://wso2.org/library/234, http://wso2.org/library/174, http://wso2.org/library/255. • The itest in the ws-binding-axis2 module and the helloworld-ws-service-secure have definitions.xml file that define the intents and policyset for confidentiality. Change the values that have been provided in the Axis2ConfigParam policy attachment, to suit what you have defined for your application – such as the keystore, the userid and password to the keystore, the password callback handler class etc. • Now, specify the confidentiality intent on any of the binding.ws elements in your application composite and ensure that the bcprov
