I didn't get any responses back on this so I rethought the problem. Instead of 
trying to include the extra data in the security tags I added a company 
specific section to the soap header just like I would do in a plain web 
service. Is there a more appropriate / standard was to do this or is this the 
normal method?

The soap header now looks like this:

<soapenv:Header>
        <wsse:Security 
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
 soapenv:mustUnderstand="1">
                <wsu:Timestamp 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
                        <wsu:Created>2006-02-02T19:36:24.281Z</wsu:Created>
                        <wsu:Expires>2006-02-03T19:36:24.281Z</wsu:Expires>
                </wsu:Timestamp>
                <wsse:UsernameToken>
                        <wsse:Username>TestSystem</wsse:Username>
                        <wsse:Password 
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>password</wsse:Password>
                </wsse:UsernameToken>
        </wsse:Security>
        <ns1:ArjisHeader xmlns:ns1="http://external.wsinterface.arjis.org"; 
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; 
soapenv:mustUnderstand="0">
                <ns1:agency>TestAgency</ns1:agency>
                <ns1:user>TestUser</ns1:user>
                
<ns1:application>ArjisRecordUpdateTestClient.echo()</ns1:application>
                <ns1:tranactionId>3</ns1:tranactionId>
                <ns1:action>Update</ns1:action>
        </ns1:ArjisHeader>
</soapenv:Header>



Thanks,
Dustin

>>> "Dustin Henson" <[EMAIL PROTECTED]> 01/31/06 3:16 PM >>>
I've been doing web services with AXIS for some time, but am new to WS-Security 
and WSS4J. I hope you gurus can point me in the right direction here.

In our current security model we have required fields besides user name and 
password, such as company name. I realize that a standard LDAP configuration 
would look this up based on the user name, but some unique security 
requirements mean that we need to spell it out in the in the raw message. Can 
someone point me to the documentation for either inserting additional fields to 
the UsernameToken section or to how to formally extend it.

Thanks,
Dustin




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to