2 Replies Latest reply on Sep 23, 2008 1:29 PM by Alessio Soldano

    Username Token Profile URIs in SOAP header not compatible?

    Joshua Stewart Newbie

      I'm writing a client to chat with a service written in .NET that utilizes Username Token Profile 1.0. I'm using JBossWS for my side of the pond. I have everything working, but when it creates the SOAP header that contains the password, it sets Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0#PasswordText".

      The .NET service seems to be looking for Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText', which is from the Username Token Profile 1.0 spec.

      Why is JBossWS putting this URI on the node of the header? Shouldn't it be conforming to the Username Token Profile 1.0 spec that is part of the WS-Security 1.0 spec?