-
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
Message "Security_Authenticate #147
Comments
Hi, Do you have the Security_Authenticate message in your WSDL? However, often it's not necessary to call Security_Authenticate explicitly when you have a WSAP configured with SoapHeader 4. If that is the case, just call the message you want to call, and the library will handle authentication and session management automatically. |
hi, i've got from amadeus only the credentials to access the extranet. |
Well, what do you want to do? Do you want to build an online booking engine? In that case you can look at this comment I made previously, which gives some recommendations on how to start building one. |
ok
|
You have configured your client to use SoapHeader 2. For SoapHeader 2, you have to send your own authentication message. Are you sure the WSDL that was given to you is a SoapHeader 2 WSDL? You can ask Amadeus which SoapHeader version it uses. if the WSDL is for SoapHeader 4, you have to configure the client to use SoapHeader 4: https://github.com/amabnl/amadeus-ws-client/blob/master/docs/about-get-started.rst#set-up-a-test-client: 'soapHeaderVersion' => Client::HEADER_V4, |
i'm waiting for their response |
and i have this error
|
Looks like your WSDL file is including an XSD file which it can't find. You have to extract the zip file you got from Amadeus, put it somewhere the client can read it, and make sure all the XSD's in the zip file are also present as they were in the zip file. It's also possible that the XSD you mention just isn't present in the WSDL:
EDIT: also, you're working with the POC (Proof of Concept) WSDL? You might have some issues with that one, because as far as I know, it includes tens of messages nobody ever uses. You might want to ask for a dedicated WSDL for your application. |
thanks but now i have an error when using $opt = new AirMultiAvailabilityOptions([
'actionCode' => AirMultiAvailabilityOptions::ACTION_AVAILABILITY,
'requestOptions' => [
new RequestOptions([
'departureDate' => \DateTime::createFromFormat('Ymd-His', '20180320-000000', new \DateTimeZone('UTC')),
'from' => 'BRU',
'to' => 'LIS',
'requestType' => RequestOptions::REQ_TYPE_NEUTRAL_ORDER
])
]
]);
$availabilityResult = $client->airMultiAvailability($opt);
|
Have you provided the password correctly (base_64 encoded)? This error is also returned when it's an authentication failure. |
Do you have an update for me? |
Hi and sorry for the late reply, |
hi @DerMika i have a couple of questions for you if you don't mind; thank you |
Yes, they are the credentials. I don't know, what do you want to do? Build an on-line booking engine? If so, then the Fare_MasterPricerTravelBoardSearch is probably the best message to start with. But before you start doing that, maybe ask Amadeus some directions. They have some implementation guides and flowcharts they can provide that you can use as a guideline. |
Is your problem fixed now? If so, can you close this issue? |
yes thank you for your support. |
hi,
i'm starting to use your sdk but i always get this error message
thanks in advance
The text was updated successfully, but these errors were encountered: