Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > About Siebel Authentication and Session Management SOAP Headers > Examples of Using SOAP Headers for Authentication and Session ManagementThe following examples illustrate using Siebel Authentication and Session Management SOAP headers. These examples use various authentication and session type combinations. For more information, see Combinations of Session Types and Authentication Types. Anonymous Request No SessionThis example illustrates an anonymous request and a session type of None, which closes the session after the response is sent out: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Siebel Authorization No SessionThis example illustrates a request that includes authentication credentials (username and password) and a session type of None, which closes the session after the response is sent out: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Siebel Authorization Stateless SessionThe following examples illustrate a request, response, and subsequent request for a session type set to Stateless, which keeps the session open after the initial response is sent out. Initial RequestThis example illustrates the initial request that includes authentication credentials (username and password) needed to log in: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> ResponseThis example illustrates the session token (encrypted) generated by the Siebel Server and sent back in the SOAP header of the response: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Subsequent Request Using Session TokenThis example illustrates a subsequent request that includes the encrypted session token that was generated by the Siebel Server and passed in a previous response. The session token includes the user credentials and session information needed to reconnect to an existing session, or log in to a new one if the initial session has been closed: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Siebel Authorization Stateful SessionThe following examples illustrate a request, response, and subsequent request for a session type set to Stateful, which keeps the session open after the initial response is sent out. Initial RequestThis example illustrates the initial request that includes authentication credentials (username and password) needed to log in: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> ResponseThis example illustrates the session token (encrypted) generated by the Siebel Server and sent back in the SOAP header of the response: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Subsequent Request Using Session TokenThis example illustrates a subsequent request that includes the encrypted session token that was generated by the Siebel Server and passed in a previous response. The session token includes the user credentials and session information needed to reconnect to an existing session: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> Simple Query Starting With <soap:body>This example illustrates data for a simple query starting with the <soap:body> element: <soap:body> |
![]() ![]() |
Integration Platform Technologies: Siebel Enterprise Application Integration | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |