[
https://issues.apache.org/jira/browse/RAMPART-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated RAMPART-361:
------------------------------------
Fix Version/s: (was: 1.7.0)
1.7.1
> Rampart can not accept Username token which is generated from WCF client. Due
> to name space qualified password type attribute in username token
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-361
> URL: https://issues.apache.org/jira/browse/RAMPART-361
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.6.0
> Environment: VS 2010
> Reporter: asela pathberiya
> Fix For: 1.7.1
>
> Attachments: RAMPART-361.patch
>
>
> Error
> Caused by: org.apache.ws.security.WSSecurityException: An invalid security
> token was provided (Bad UsernameToken Values)
> at
> org.apache.ws.security.message.token.UsernameToken.<init>(UsernameToken.java:182)
> at
> org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:96)
>
> This is generated in WSS4j . "allowNamespaceQualifiedPasswordTypes" property
> in WSSConfig object that is handover to "UsernameToken" class ; is false.
> But for the username token that is generated from WCF client, that property
> must be true. Therefore i hope it must be handle at rampart level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
