Configuring Siebel to Integrate with Oracle Publisher for Web Single Sign-On

The following procedure shows how to configure your Siebel application so that it can integrate with Oracle Publisher when Web Single Sign-On (SSO) authentication is being used.

To configure Siebel to integrate with Oracle Publisher in Web SSO environment

  1. For the Security Adapter Profile (LDAP Security Adapter profile) that is used for authentication and Web SSO, specify parameter values as shown in the following table.

    Parameter Name Value

    Single Sign On

    True

    Trust Token

    password

    This is the value of the TrustToken parameter used for SSO in the Application Interface profile.

  2. For the server components listed in the following table, specify values for the parameters shown. Specify values for the LDAP security adapter.

    Server Component Parameter Value

    Application Object Manager and EAI Object Manager

    Security Adapter Name

    LDAPSecAdpt

    Application Object Manager and EAI Object Manager

    Security Adapter Mode

    LDAP

    Application Object Manager and EAI Object Manager

    Username

    LDAP_USER_ID

    Application Object Manager and EAI Object Manager

    Password

    password

    The password associated with the LDAP_USER_ID.

    XMLP Report Server

    Security Adapter Name

    LDAPSecAdpt

    XMLP Report Server

    Security Adapter Mode

    LDAP

    XMLP Report Server

    Username

    LDAP_USER_ID

    XMLP Report Server

    Password

    password

    This is the value of the TrustToken parameter used for SSO in the Application Interface profile.

    Note: The LDAP_USER_ID values you specify must be an LDAP user who has a Siebel employee record, for example, AnonUserName, in the Application Interface profile.
  3. In the [/eai_lang] section of the Application Interface profile, remove the following parameters:

    Parameter Name Value

    Single Sign On

    False

    Trust Token

    TrustToken_Value

    UserSpec

    HTTP Header Variable

    User SpecSource

    Header

    Tip: Ensure that the redirection to SSO server for the Application Interface profile is not set up on the Siebel Application Interface.
    Note: The Siteminder ERP Agent for Siebel (also known as Web Agent) and the Siteminder Policy Server is still used to obtain the User Identity in the form of a HTTP header variable called SIEBELUSER and SSO Authentication Ticket.
  4. Restart the Siebel Server, and the Application Interface.

  5. When the services are started, verify that the Application Object Manager, EAI Object Manager, and XMLP Report Server components are online.

    If any of these services are unavailable, create a service request (SR) on My Oracle Support. Alternatively, you can phone Oracle Global Customer Support directly to create a SR or get a status update on your current SR. Support phone numbers are listed on My Oracle Support.