Siebel Mobile Connector Guide > Working with the Siebel Mobile Connector > Real-Time Access to Data >

Authenticating Users

Authentication is the process of verifying the identity of a user. The Siebel Mobile Connector uses the Siebel security adapter authentication architecture for authenticating Siebel application users to external partner applications. This architecture supports authentication to Microsoft Active Directory Server and LDAP-compliant directories. Additionally, partners may also create their own authentication mechanism by writing to the Siebel Security Adapter API. For more information, go to and perform a browse/search for Security Adapter SDK.

Partner applications must log in to the Siebel Web Engine to instantiate a user session and must log out to terminate the session. A user's session is managed in SWE by using cookies or an authentication mode without cookies.

Logging In

Logging in to SWE is required to instantiate a new user session. The command ExecuteLogin is used to supply the user credentials and log in.

The following is an example of how to construct a log in command by using an HTTP request.

To log in to SWE

  • Send the ExecuteLogin command in a HTTP request to SWE, with a valid user name and password.

    In the following example, your user name and password is WLEE.


    NOTE:  SWESetMarkup is a required parameter. Generally, when using the Siebel Mobile Connector you can set the SWESetMarkup parameter to HTML, WML, or XML. However, you may not use the GetSMCUpdate method or receive alerts in any other markup than XML.

Logging Off

Logging off of SWE is required to terminate a new user session. The command Logoff is used to log off.

To log off from SWE

  • Send the Logoff command in a HTTP request to SWE.


NOTE:  There is a default time-out set by the SWE engine if no user action has taken place.

Session Management

When a user logs in to the Siebel Web Engine, SWE dynamically generates session cookies or uses an authentication mode without cookies. Cookies are generated by default and include a Session ID that is used to track the session. If cookies are disabled or if a user's browser does not support cookies, then the Session ID for each page is included in its URL.

For more information, refer to Security Guide for Siebel eBusiness Applications.

Siebel Mobile Connector Guide