Hi,
See my comments below.
Samisa Abeysinghe wrote:
Kaushalye Kapuruge wrote:
Hi All,
This is a briefing about current status and what is ahead in
implementing Rampart/C.
What is done?
------------------------
Rampart supports
1. Username tokens with plain text and digested passwords
2. Timestamp tokens
3. Password callback mechanism
4. Both dynamic and static configurations
Could you please elaborate on point 4. What are configured?
User need to configure some parameters. For example the user name,
passwordType, Callback class etc.
See INSTALL file for more information.
See rampart/samples/client/data/axis2.xml for a sample configuration.
What is the difference between dynamic and static?
Static configurations => Configurations using the axis2.xml file.
Dynamic configurations => In the client level it is possible to set
option parameters using
AXIS2_OPTIONS_SET_PROPERTY(). See the echo client sample under
rampart/samples/client/echo.
Always static configurations are overridden by dynamic configurations.
What is ahead?
-------------------------
Support for
1. Encryption
2. Signing SOAP messages.
Current status
-------------------------
For encryption and signing it is necessary to have a xml security
library. So I'm implementing such for AXIOM, named omxmlsec.
Omxmlsec uses openssl as the crypto library. I managed to write a
wrapper library for openssl encryption. Right now I'm coding for
omxmlsec library. After this I have to write code for Rampart/C that
supports encryption.
Would omxmlsec be part of Rampart/C section of Axis2/C svn tree, or is
it on a different project?
It is part of the Rampart/C section. Serves as a xml security library.
Thanks,
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
