Custom UsernameToken?

[Justin Olomar]

We would like to use the UsernameToken WS-Security standard to implement security in our web services. The only hitch is that we need more than just a username and password...we need a CompanyID, also. Is it possible to create a custom UsernameToken element in the SOAP headers and still be compliant with the WS-Security standards? I apologize if I have not used the correct terminology...hopefully this makes sense.

We are using Tomcat 6, Axis2 v1.5 and Rampart. As an example, we would like the header to look something like this:

<soap12:Header>
  <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Id-000001239b40674e-000000000097cc12-8">
      <wsse:Username>ws</wsse:Username>
      <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">security</wsse:Password>
      <wsu:CompanyID>123456</wsu:CompanyID>
    </wsse:UsernameToken>
  </wsse:Security>
</soap12:Header>

Thank you,
Justin

[Ulf Dittmer]

No, I don't think that's allowed. But nothing stops you from adding your own custom SOAP header that's outside of the wsse:Security header.

[Justin Olomar]

Ulf Dittmer wrote:No, I don't think that's allowed. But nothing stops you from adding your own custom SOAP header that's outside of the wsse:Security header.

Thank you for the reply. So if we add our own custom headers to accomplish what we want, will our web service still be SOAP compliant and be able to be easily accessed via Java OR .NET clients? (If you can't tell, I'm new to this sort of thing )

[Ulf Dittmer]

SOAP specifically allows adding custom headers; you may want to read through the SOAP spec for the details - it's not long or complicated.

[Justin Olomar]

Ulf Dittmer wrote:SOAP specifically allows adding custom headers; you may want to read through the SOAP spec for the details - it's not long or complicated.

Thanks Ulf, you've pointed me in the right direction....hopefully.