You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2009/04/03 13:46:13 UTC
[jira] Assigned: (WSS-131) no support for extension of
SecurityHeader
[ https://issues.apache.org/jira/browse/WSS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh reassigned WSS-131:
---------------------------------------
Assignee: Colm O hEigeartaigh (was: Ruchith Udayanga Fernando)
> no support for extension of SecurityHeader
> ------------------------------------------
>
> Key: WSS-131
> URL: https://issues.apache.org/jira/browse/WSS-131
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Handlers
> Affects Versions: 1.5.6
> Reporter: Lisa Penninger
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.7, 1.6
>
>
> The WSS SecurityHeader schema definition is extensible to allow different types of security information to be included, i.e., I could define a FooToken in my schema and include it in the SecurityHeader in addition to my UsernameToken. However, wss4j seems to actively prevent this, throwing an exception if an unrecognized token is found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org