sabre - Authentication error on EnhancedAirBookRQ -


i used binarysecuritytoken enhancedairbookrq, receive usg_authorization_failed. used same token bargainfindermaxrq , worked. should set of test credentials sequence provided here?

request:

<soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"               xmlns:sec="http://schemas.xmlsoap.org/ws/2002/12/secext"               xmlns:mes="http://www.ebxml.org/namespaces/messageheader"               xmlns:ns="http://www.opentravel.org/ota/2003/05"> <soapenv:header>     <sec:security>         <sec:binarysecuritytoken>--token--</sec:binarysecuritytoken>     </sec:security>     <mes:messageheader>         <mes:from>             <mes:partyid type="urn:x12.org:io5:01">from</mes:partyid>         </mes:from>         <mes:to>             <mes:partyid type="urn:x12.org:io5:01">ws</mes:partyid>         </mes:to>         <mes:cpaid>--cpaid--</mes:cpaid>         <mes:conversationid>eservices@sabre.com</mes:conversationid>         <mes:service mes:type="sabrexml">sabrexml</mes:service>         <mes:action>enhancedairbookrq</mes:action>         <mes:messagedata>             <mes:messageid>00000</mes:messageid>             <mes:timestamp>233</mes:timestamp>         </mes:messagedata>         <mes:description xml:lang="en-us">testing</mes:description>     </mes:messageheader> </soapenv:header> <soapenv:body>     <enhancedairbookrq version="3.7.0" haltonerror="true">         <ota_airbookrq>             <origindestinationinformation>                 <flightsegment departuredatetime="2016-11-15t10:05:00" flightnumber="241" numberinparty="2"                                resbookdesigcode="f" status="nn">                     <destinationlocation locationcode="atl"/>                     <marketingairline code="us" flightnumber="241"/>                     <originlocation locationcode="las"/>                 </flightsegment>             </origindestinationinformation>         </ota_airbookrq>     </enhancedairbookrq> </soapenv:body> 

response:

<soap-env:envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:header>     <eb:messageheader eb:version="1.0" soap-env:mustunderstand="1"                       xmlns:eb="http://www.ebxml.org/namespaces/messageheader">         <eb:from>             <eb:partyid eb:type="uri">ws</eb:partyid>         </eb:from>         <eb:to>             <eb:partyid eb:type="uri">from</eb:partyid>         </eb:to>         <eb:cpaid>--cpaid--</eb:cpaid>         <eb:conversationid>eservices@sabre.com</eb:conversationid>         <eb:service eb:type="sabrexml">sabrexml</eb:service>         <eb:action>errorrs</eb:action>         <eb:messagedata>             <eb:messageid>2308814425665870610</eb:messageid>             <eb:timestamp>2016-11-08t11:49:26</eb:timestamp>             <eb:reftomessageid>00000</eb:reftomessageid>         </eb:messagedata>     </eb:messageheader>     <wsse:security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext">         <wsse:binarysecuritytoken valuetype="string" encodingtype="wsse:base64binary">--token--</wsse:binarysecuritytoken>     </wsse:security> </soap-env:header> <soap-env:body>     <soap-env:fault>         <faultcode>soap-env:client.authorizationfailed</faultcode>         <faultstring>authorization failed</faultstring>         <detail>             <stacktrace>com.sabre.universalservices.base.security.authorizationexception:                 errors.authorization.usg_authorization_failed             </stacktrace>         </detail>     </soap-env:fault> </soap-env:body> 

do have api agreement? looks credentials don't have appropiate authorization consume service.

in case have contract, i'd advise contact helpdesk can revise credentials.


Comments

Popular posts from this blog

How to get the arclen between two curve points in Maya? -

C++ Linked List -

git svn - Unignore directories in git-svn (adding directories to a sparse checkout) -