Table 11. Summary of Authentication Types and Session Types
|
|
|
None |
None |
A single request is sent with an anonymous user login, and the session is closed after the response is sent out. In order for the anonymous session to be identified by the SWSE Plug-in, UsernameToken and PasswordText must be excluded in the SOAP headers. |
Username and password |
None |
A single request is sent with the username and password used to log in, and the session is closed after the response is sent out. |
Username and password |
Stateless |
The initial request to log in establishes a session that is to remain open and available for subsequent requests. Username/password are used to log in and a session token is returned in a SOAP header included in the outbound response. The session remains open. |
Session token (stateless) |
Stateless |
Request to reconnect to an established session, using the information contained in the session token. If the session has been closed, then automatic relogin occurs. The Siebel servers include the session token in the SOAP header of the response. The session remains open. |
Session token (stateless) |
None |
When a SOAP header carries a session token and has the session type set to None, then the Session Manager on the SWSE closes (logs out) of this session, and invalidates the session token. The session token is not used after the session is invalidated. |