Tangoe Telecom SOAP API

Telecom web services can receive unauthenticated requests if configured so, but a new configuration is also available based on the Oasis Web Services Security – UsernameTokenProfile specification. In the secured version, we expect an UsernameToken element in the header, containing the following:

• The username
• The password

The Password element include the PasswordDigest created using the following formula:

             Password\_Digest = Base64 (SHA-1 (nonce + created + hex(SHA-256 (password)) ) )

Please note that the standard specification doesn’t include the hex(SHA256) transformation of the password. For example the hex representation of the SHA256 of password "a" is: "ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb"

A sample request to get the available service types, can be seen below:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <wsse:Security xmlns:wsse="http://docs.oasis- open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
            xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity- utility-1.0.xsd" SOAP-ENV:mustUnderstand="1">
            <wsse:UsernameToken wsu:Id="UsernameToken- 455E8909E1F6E53F6614391911304261">
                <wsse:Username>guest</wsse:Username>
                <wsse:Password Type="http://docs.oasis- open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">S5A3tTxe1GWCjYp22HMA7e1P+DI=</wsse:Password>
                <wsse:Nonce EncodingType="http://docs.oasis- open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">vGLJ6YTnyVtmyLSzRqIJzA==</wsse:Nonce>
                <wsu:Created>2015-08-10T07:18:50.422Z</wsu:Created>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <ns2:GetServiceTypesRequest xmlns:ns2="http://www.asentinel.com/asentinelws/schemas/invord"/>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>