[ 
https://issues.apache.org/jira/browse/RAMPART-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272404#comment-13272404
 ] 

Graeme Jenkinson edited comment on RAMPART-205 at 5/10/12 3:06 PM:
-------------------------------------------------------------------

With the changes made to WSSConfig in version 1.6, I can't see anyway in 
Rampart whether programmatically or declaratively to change the WSSConfig used 
by the WSSecurityEngine instance. I see that as fairly significant as, for 
example, the Processors and Valiadtors can't be changed from their default 
settings.


                
      was (Author: graemejenkinson):
    With the changes made to WSSConfig in version 1.6, I can't see anyway in 
Rampart whether programmatically or declaratively to change the WSSConfig used 
by the WSSecurityEngine instance. I see that as fairly significant as, for 
example, the Processors and Valiadtors can't be changed from their default 
settings.
                  
> Setting WSSConfig properties from RampartConfig
> -----------------------------------------------
>
>                 Key: RAMPART-205
>                 URL: https://issues.apache.org/jira/browse/RAMPART-205
>             Project: Rampart
>          Issue Type: Improvement
>            Reporter: Frode Laukus
>            Priority: Minor
>
> I believe it's not currently possible to set properties on WSS4J WSSConfig 
> using the RampartConfig. I think it would be a nice improvement to be able to.
> One example is WSSConfig.HANDLE_CUSTOM_PASSWORD_TYPES which I recently found 
> I would have liked being able to set to true, being default false.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to