You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2017/07/30 22:18:00 UTC
[jira] [Updated] (RAMPART-361) Rampart can not accept Username
token which is generated from WCF client. Due to name space qualified
password type attribute in username token
[ 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.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
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org