[wsf-c-dev] Current status of Rampart/C

Kaushalye Kapuruge kaushalye at wso2.com
Tue Jan 16 06:08:25 PST 2007


Hi list,
Following will describe the current status of Rampart/C

Recent modifications:
Recently I've introduced an authentication module, which can be used to 
authenticate an incoming username token. Rampart will load the 
authentication module dynamically and plug it to the username token 
verification process. Just like the way we used the password callback 
module. But with a little difference.
Instead of giving just the username to pick the password, we will 
provide both the username and the password. The module will validate the 
pair and return a status code. There are two methods to implement by the 
module writer for both plaintext passwords and the digests.
Under rampart/samples/authn_provider there is a sample implementation 
for this.
The next step is to write a credential module for the message outgoing 
case. Both these were raised in JIRA - 
http://issues.apache.org/jira/browse/AXIS2C-261

There are few changes in OMXMLSecurity to extract x509 certificates/keys 
from a buffer. This is done specifically to support the PHP extension.

Security-Policy integration:
We are almost at the integration level of security-policy with rampart. 
The security-policy code will be committed to the svn this week.

XML-Signature and Canonicalization:
We have planned to locate the C14N implementation under the 
OMXMLSecurity library. After that we will start the XML-Signature 
implementation in OMXMLSecurity and then later use it in Rampart/C.


Cheers,
Kaushalye


 







More information about the Wsf-c-dev mailing list