[
https://issues.apache.org/jira/browse/WSS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Tew closed WSS-451.
--------------------------
Resolution: Not A Problem
Seems like adding known prefixes to elements is a generally accepted practice.
Some applications may rely on specific prefixes. So I am happy to work around
this adding the wsse namespace declaration at a different level. Thanks for the
explanation. In general elements are tied to a namespace and the prefix is not
relevant.
> Fixed namespace prefix when creating elements in SecurityTokenReference.java
> ----------------------------------------------------------------------------
>
> Key: WSS-451
> URL: https://issues.apache.org/jira/browse/WSS-451
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 1.6.10
> Environment: windows/java used by apache cxf sts
> Reporter: Arthur Tew
> Assignee: Colm O hEigeartaigh
> Priority: Critical
> Labels: newbie
>
> line 443 reads Element keyId = doc.createElementNS(WSConstants.WSSE_NS,
> "wsse:KeyIdentifier");
> should read : doc.createElementNS(WSConstants.WSSE_NS, "KeyIdentifier");
> line 118 reads element = doc.createElementNS(WSConstants.WSSE_NS,
> "wsse:SecurityTokenReference");
> should read element = doc.createElementNS(WSConstants.WSSE_NS,
> "SecurityTokenReference");
> When a token is generated and the wsse namespace is assigned to a different
> prefix or is the default namespace the explicit tokens cause validations to
> fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
