Siebel Security Guide > Web Single Sign-On Authentication > Configuring Siebel CRM and Oracle BI Publisher for Web Single Sign-On >

Configuring Siebel CRM for Integration with Oracle BI Publisher with Web Single Sign-On

This topic describes the configuration tasks you must perform for your Siebel application so that it can integrate with Oracle BI Publisher when Web Single Sign-On authentication is implemented.

To configure Siebel CRM for BI Publisher integration in a Web SSO environment

1. For the Security Adapter Profile (either the LDAP Security Adapter profile or the ADSI Security Adapter profile) that is used for authentication and Web SSO, specify parameter values similar to those shown in the following table.

   Parameter Name	Value
   Single Sign On	True
   Trust Token	password This is the value of the TrustToken parameter (in encrypted format) this is specified in the eapps.cfg file.

2. For the server components listed in the following table, specify values for the parameters shown. Specify values either for the LDAP or for the ADSI security adapter, depending upon the security adapter you have implemented.

   Server Component	Parameter	Value
   Application Object Manager and EAI Object Manager	Security Adapter Name	Either LDAPSecAdpt or ADSISecAdpt
   	Security Adapter Mode	LDAP or ADSI
   	Username	LDAP_USER_ID or AD_USER_ID
   	Password	password The password associated with the LDAP_USER_ID or AD_USER_ID
   XMLP Report Server	Security Adapter Name	LDAPSecAdpt or ADSISecAdpt
   	Security Adapter Mode	LDAP or ADSI
   	Username	LDAP_USER_ID or AD_USER_ID
   	Password	password This is the value of the TrustToken parameter (in encrypted format) specified in the eapps.cfg file.

   NOTE:  The LDAP_USER_ID or AD_USER_ID values you specify must be an LDAP or Active Directory user who has a Siebel employee record, for example, AnonUserName, in the eapps.cfg file.

3. Enable Single Sign-On for the EAI Object Manager by adding the parameters in the following table to the [/eai_lang] section of the eapps.cfg file.

   Parameter	Value
   SingleSignOn	True
   TrustToken	TrustToken_Value
   UserSpec	HTTP Header Variable
   UserSpecSource	Header

4. Restart the Siebel Server, Siebel Gateway Name Server, and the Siebel Web Server services.
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 service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support.