Configuring Rampart and Rahas in client code

[Dennis Sosnoski <dm...@sosnoski.com>]

It's often ugly to embed Rampart and Rahas configuration information 
(e.g., <ramp:RampartConfig 
xmlns:ramp="http://ws.apache.org/rampart/policy"> element, along with 
parameters such as "sct-issuer-config" used by Rahas) directly in WSDL 
or policy documents, especially when using client code generation for 
the policy handling (since the keystore information and such may change 
between development and deployment). Is there a more direct way of 
passing this configuration information through the Axis2 client API?

Thanks,

  - Dennis

-- 
Dennis M. Sosnoski
Java XML and Web Services
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117

Re: Configuring Rampart and Rahas in client code

[prabath <pr...@wso2.com>]

Hi Dennis;

You can build the RampartConfig in the code it self.

Please have a look at populateRampartConfig() method of [1].

Thanks & regards.
-Prabath

[1]: 
https://wso2.org/svn/browse/wso2/trunk/carbon-components/security/org.wso2.carbon.modules.security/src/main/java/org/wso2/carbon/security/SecurityScenarioConfigAdmin.java

Dennis Sosnoski wrote:
> It's often ugly to embed Rampart and Rahas configuration information 
> (e.g., <ramp:RampartConfig 
> xmlns:ramp="http://ws.apache.org/rampart/policy"> element, along with 
> parameters such as "sct-issuer-config" used by Rahas) directly in WSDL 
> or policy documents, especially when using client code generation for 
> the policy handling (since the keystore information and such may 
> change between development and deployment). Is there a more direct way 
> of passing this configuration information through the Axis2 client API?
>
> Thanks,
>
>  - Dennis
>