Skip to main content
Summary How to configure an Artix 4.x router to add a WS-Security header?
Article Number 29084
Environment Product: Artix Version: 4.x OS: all
Question/Problem Description I have a requirement to add a WS-Security SOAP header for every request. The WS-Security header will have a username/password pair. The SOAP request message should look like the following:

<soapenv:Header>
    <s:Security soapenv:mustUnderstand="1"
                xmlns:s="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                
        <s:UsernameToken u:Id="unt_20">
            <s:Username>theMechId</s:Username>
            <s:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
            thePassword</s:Password>
        </s:UsernameToken>
    </s:Security>
</soapenv:Header>


How can this be achieved from an Artix router?
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution In order to add a WS-Security header to a SOAP message in an Artix4.x router, add the following configuration to the Artix router configuration scope:

principal_sponsor:wsse:use_principal_sponsor = "true";
principal_sponsor:wsse:auth_method_id = "USERNAME_PASSWORD";
principal_sponsor:wsse:auth_method_data = ["username=test_username", "password=test_password"];

of course replace "test_username" and "test_password" with your own.
Workaround
Notes
Attachment
Created date: 22 February 2012
Last Modified: 13 February 2013
Last Published: 12 May 2012
First Published date: 22 February 2012

#KnowledgeDocs
#Orbix
Terms & ConditionsAccessibility statement