-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No active session #40
Comments
I had forgotten the $client->securityAuthenticate() <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://xml.amadeus.com/VLSSLQ_06_1_1A">
<SOAP-ENV:Body>
<ns1:Security_Authenticate>
<ns1:userIdentifier>
<ns1:originIdentification>
<ns1:sourceOffice/>
</ns1:originIdentification>
<ns1:originatorTypeCode/>
<ns1:originator/>
</ns1:userIdentifier>
<ns1:dutyCode>
<ns1:dutyCodeDetails>
<ns1:referenceQualifier>DUT</ns1:referenceQualifier>
<ns1:referenceIdentifier/>
</ns1:dutyCodeDetails>
</ns1:dutyCode>
<ns1:systemDetails>
<ns1:organizationDetails>
<ns1:organizationId/>
</ns1:organizationDetails>
</ns1:systemDetails>
<ns1:passwordInfo>
<ns1:dataLength/>
<ns1:dataType>E</ns1:dataType>
<ns1:binaryData/>
</ns1:passwordInfo>
</ns1:Security_Authenticate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope> <?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns="http://webservices.amadeus.com/definitions">
<SessionId>015S216GJ3|1</SessionId>
</soap:Header>
<soap:Body>
<soap:Fault xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>soap:Client</faultcode>
<faultstring>18|Presentation|Fusion DSC found an exception !\n
\tMissing Mandatory tag :\n
\tExpected element: userIdentifier\n
\tCurrent position in buffer: <ns1:dutyCode><ns1:dutyCodeDet\n
\tLast 15 characters before error: y_Authenticate>
</faultstring>
<faultactor>SI:APA</faultactor>
</soap:Fault>
</soap:Body>
</soap:Envelope> |
Hi, The thing that's going wrong is you provide an Array to the The result is that the Authentication parameters are not picked up properly. That's why you're sending an empty I realize that this is not very intuitive, and in the future I'd like to be able to provide one big nested Array for Client instantiation, but that's work in progress. Please let me know if that fixes your problem. |
Now works great. :) |
Thanks for your help. |
Ok, I found what went wrong with your security authenticate: there is an error in the documentation in the authentication parameters. I'm going to fix it now... |
… to Client AuthParams causing Security_Authenticate message to fail when using SoapHeader 2. (#40)
So the problem was that the Doing so resulted in empty authentication parameters in the Client, which resulted in a Security_Authenticate with empty parameters. This is what you experienced. I've now fixed:
|
… to Client AuthParams causing Security_Authenticate message to fail when using SoapHeader 2. (#40)
…AN-769-search-compare-add-more-data-to-all to master * commit '95773d71a6c8fb637608c9e86b7fa0a31944cda6': (change) register error logger only when needed (add) specific error logger to log information based on status code
Hello guys!
Could someone help me with this situation?
Its necessary another step to create session?
The text was updated successfully, but these errors were encountered: