Table of Contents |
---|
Overview
All messages to and from SiteConnect must be soap messages. They include a SOAP Security header for authentication purposes and contain the SOAP Body which contains the OTA message.
The following example is a complete SOAP message (this one shows an OTA_HotelAvailNotifRQ message payload)
SOAP version
SiteConnect is using SOAP 1.1
SOAP Security Header
The Security Header structure conveys authentication information. It is mandatory.
The ONLY acceptable value for the Password/@Type attribute is
"<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">SECRET</wsse:Password>
", indicating a plain text password.
Plain text passwords are acceptable as all communication is done over encrypted HTTP (HTTPS).
Security Header Example
Code Block | ||
---|---|---|
| ||
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <wsse:UsernameToken> <wsse:Username>USERNAME</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">SECRET</wsse:Password> <!-- The ONLY acceptable value for the Password/@Type attribute is Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText" --> </wsse:UsernameToken> </wsse:Security> |
Credential and Endpoint Requirements
Note |
---|
|
Full XML Sample
The following example is a complete SOAP message (this one shows an OTA_HotelAvailNotifRQ message payload):
|
|