[prev in list] [next in list] [prev in thread] [next in thread]
List: wss4j-dev
Subject: [jira] Updated: (WSS-131) no support for extension of
From: "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date: 2009-06-25 11:21:07
Message-ID: 449103501.1245928867480.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/WSS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Colm O hEigeartaigh updated WSS-131:
------------------------------------
Affects Version/s: (was: 1.5.6)
1.5.7
Fix Version/s: 1.5.8
> 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.7
> Reporter: Lisa Penninger
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.8, 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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic