[ http://jira.codehaus.org/browse/XFIRE-149?page=all ]
Dan Diephouse closed XFIRE-149:
-------------------------------
Resolution: Fixed
> WS-Security implementation
> --------------------------
>
> Key: XFIRE-149
> URL: http://jira.codehaus.org/browse/XFIRE-149
> Project: XFire
> Type: New Feature
> Reporter: Tomasz Sztelak
> Assignee: Tomasz Sztelak
> Fix For: 1.1-beta-1
> Attachments: wssecurity.zip, xfire-ws-security-patch-20060104-1305.txt
>
>
> Inside the patch there is some code which implements part of WS-Security
> (encryption/decryption) . Its not fully functional yet and its posted just to
> show the idea and get some feedback :) Implementation is based on wss4j
> library and use property file config which give details of private/public key
> location and type. Usage in application looks like this :
> <inHandlers>
> <handler
> class="org.codehaus.xfire.security.wssecurity.WSS4jInSecurityHandler" />
> <inHandlers>
> <outHandlers>
> <handler
> class="org.codehaus.xfire.security.wssecurity.WSS4JOutSecurityHandler"/>
> </outHandlers>
> Config file :
> xfire.security.keystore.password=keystorePass
> xfire.security.keystore.file=META-INF/xfire/privatestore.jks
> xfire.security.key.alias=alias
> xfire.security.key.password=aliaspass
> Encryption/decryption code implements InSecurityProcessor
> /OutSecurityProcessor interfaces ( there are a processor property in Handlers
> ) , so can be easly replaced with other implementation.
> Above processor are build by builder class ( builder property o processor
> class ) and also can be replaced with any imlementation ( e.g. which get the
> public/private key from ldap or any other storege ).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
