OSD WSDL Generation Omits Required Username And Password Tags (Doc ID 1527352.1)

Last updated on AUGUST 04, 2014

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of OSD (Open Services Development), there are two ways to authenticate requests from ASPs (Application Service Providers):

1. Encoding/decoding of the Username/Password in the HTTP (HyperText Transfer Protocol) header send with the SOAP (Simple Object Access Protocol) message (note the Authorization in the HTTP header):

POST / HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://host-sms01.us.oracle.com/wsdls/Boss/MyOperationSet/TriggerAControlPlan"
Authorization: Basic MmRlZ3JlZXM6Y2hpbGx5
Content-Length: 401
Host: host-slc01.us.oracle.com:4099
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ger="http://host-sms01.us.oracle.com/wsdls/Boss/MyOperationSet.wsdl">
   <soapenv:Header/>
   <soapenv:Body>
      <ger:TriggerAControlPlanRequest>
         <CC_Calling_Party_Id>64123456789</CC_Calling_Party_Id>
      </ger:TriggerAControlPlanRequest>
   </soapenv:Body>
</soapenv:Envelope

 2. Explicitly sending the Username/Password in the SOAP body (note the username/password XML nodes in the SOAP body)

POST / HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://host-sms01.us.oracle.com/wsdls/Boss/MyOperationSet/TriggerAControlPlan"
Content-Length: 473
Host: host-slc01.us.oracle.com:4099
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ger="http://host-sms01.us.oracle.com/wsdls/Boss/MyOperationSet.wsdl">
   <soapenv:Header/>
   <soapenv:Body>
      <ger:TriggerAControlPlanRequest>
         <username>name</username>>
         <password>word</password>>
         <CC_Calling_Party_Id>64123456789</CC_Calling_Party_Id>
      </ger:TriggerAControlPlanRequest>
   </soapenv:Body>
</soapenv:Envelope>

Both methods are valid and work with OSD, however there is no way to generate the WSDL (Web Services Description Language) for the second method.

The only WSDL generated by NCC does not contain the username/password XML tags.  For example:

...
       <xs:complexType name="TriggerAControlPlanRequestType">
            <xs:sequence>
                <xs:element name="CC_Calling_Party_Id" type="oracle:NumericString" minOccurs="1"/>
            </xs:sequence>
        </xs:complexType>
...

Changes

Attempt to generate WSDL for ASPs to invoke service logic through OSD.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms