Configuring SAP SSO
Configuring SAP SSO
Configuring SAP SSO
Overview
This document provides information and instructions for setting up Kerberos end-to-end Single Sign-On (SSO) using IIS to the database level for BusinessObjects Enterprise XI and XI Release 2. This feature allows you to log on to InfoView without being prompted for a username and password. Furthermore, the users credentials are passed on to the database for authentication, allowing the database administrator to set restrictions based on the users credentials.
Contents
INTRODUCTION ............................................................................................ 1 CONFIGURING ACTIVE DIRECTORY ............................................................... 1 Determining the AD domain functional level ......................................1 Creating the Service Account .................................................................1 Windows 2000 domain functional level ................................................1 Windows 2003 domain functional level ................................................2 Registering the Service Principle Name (SPN) ...................................3 CONFIGURING THE BUSINESSOBJECTS ENTERPRISE SERVER........................ 5 Configuring local security policies .........................................................5 Configuring BusinessObjects Enterprise services ...............................5 CONFIGURING INTERNET INFORMATION SERVICE (IIS)................................... 7 Enabling Windows Authentication .......................................................7 Configuring the IIS application pool......................................................7 Modifying the web.config file ..................................................................8 CONFIGURING THE ACTIVE DIRECTOR PLUG-IN IN THE CMC ......................... 9 CONFIGURING THE INTERNET EXPLORER BROWSER ON THE CLIENT ............. 10 TROUBLESHOOTING .................................................................................. 11 Looping logon ............................................................................................11 Service unavailable error message .........................................................11 Reports with LOV prompts fail .................................................................12 RAS service does not start .........................................................................12 FINDING MORE INFORMATION ..................................................................... 12
6/26/2007 9:13 AM
Introduction
End-to-end SSO refers to a configuration where users have both SSO access using IIS in this case to BusinessObjects Enterprise and the backend databases. Thus, users need to provide their logon credentials only once when they log on to the operating system, to access BusinessObjects Enterprise and the databases. In BusinessObjects Enterprise, end-to-end SSO is supported through Windows Active Directory (AD) and Kerberos using IIS. There are some prerequisites that you need before you begin: Administrative rights to the AD domain controller. Administrative rights to the BusinessObjects Enterprise system. SQL Server Trusted Connection ODBC System DSN using Windows NT authentication using the Network Login ID option. See your database administrator regarding that.
6/26/2007 9:13 AM
Page 1
boe_xi_r2_end_to_end_sso.pdf
2. Navigate to the Users container and click the Create a new user in the current container button on the toolbar. 3. Click Properties > Account > Account is trusted for delegation > Password never expires. See figure 1. Figure 1:
4. Clear the option User must change password at next logon and click OK.
Page 2
boe_xi_r2_end_to_end_sso.pdf
3. For the newly created user click Properties > Delegation > Trust this user for delegation to any service (Kerberos only) > OK. See Figure 2. Figure 2:
http://www.microsoft.com/downloads/details.aspx?familyid=5fd8 31fd-ab77-46a3-9cfe-ff01d29e5c46 b. For Windows 2003 download it from the link below or search for setspn download at http://www.microsoft.com:
6/26/2007 9:13 AM
Page 3
boe_xi_r2_end_to_end_sso.pdf
http://www.microsoft.com/downloads/details.aspx?FamilyId=6E C50B78-8BE1-4E81-B3BE-4E7AC4F0912D. 2. Click Start > Programs > Accessories > Command Prompt and run SETSPN using the following syntax: SETSPN.exe A BOBJCentralMS/HOSTNAME.DOMAIN.COM ServiceCMS
NOTE
Replace ServiceCMS with the actual account name that is trusted for delegation and replace HOSTNAME with the name of your machine running the CMS service. The output of the file is as follows: Registering ServicePrincipalNames for CN=ServiceCMS,CN=Users,DC=DOMAIN,DC=COM BOBJCentralMS/HOSTNAME.DOMAIN.COM Updated object
1. Run SETSPN to register the hostname of the Business Objects server without using the fully qualified name as follows: SETSPN.exe A BOBJCentralMS/HOSTNAME ServiceCMS 2. Run SETSPN to register HTTP using the following command: SETSPN.exe A HTTP/HOSTNAME.DOMAIN.COM ServiceCMS
NOTES
For information on why you must register HTTP as an SPN, search for Microsoft knowledge base article 871179 at the link below: http://www.microsoft.com/
Type SETSPN.exe L ServiceCMS to get a listing of what is currently registered for the ServiceCMS account. Remember to replace ServiceCMS with the actual account name that is trusted for delegation.
6/26/2007 9:13 AM
Page 4
boe_xi_r2_end_to_end_sso.pdf
To configure local security policies do the following: 1. Click Start > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment. 2. Double-click Act as part of the operating system. 3. Click Add, add the user account thats been trusted for delegation, and click OK. 4. Repeat the steps 1-3 for the Logon as service right.
To configure any of these services to run under the domain account, follow these steps:
6/26/2007 9:13 AM
Page 5
boe_xi_r2_end_to_end_sso.pdf
1. On the BusinessObjects Enterprise server click Start > Programs > Business Objects XI > BusinessObjects Enterprise > Central Configuration Manager. 2. In the Central Configuration Manager, stop the CMS, right-click the service, click Properties, and under Log On As clear the System Account check box. See Figure 4. 3. Type the username and password for the account that is trusted for delegation. For example, DOMAIN\ServiceCMS. See Figure 4. Figure 4:
4. Click OK and start the service. 5. Repeat the process for the Crystal Reports Page Server, Web Intelligence Report Server, RAS, Connection Server (Enterprise XI Release 2 only) and Desktop Intelligence Report Server (Enterprise XI Release 2 only) services.
NOTE
The RAS server may fail to start under this new service account. If you experience this issue, follow the steps outlined in the following kbase: http://support.businessobjects.com/library/kbase/articles/c2018785.asp
6/26/2007 9:13 AM
Page 6
boe_xi_r2_end_to_end_sso.pdf
6/26/2007 9:13 AM
Page 7
boe_xi_r2_end_to_end_sso.pdf
Figure 5:
NOTE
You may receive the error message Service unavailable when launching InfoView after changing the identity of the application pool to the new service account. If this is the case, you will have to add this service account to the IIS_WPG group on the IIS server.
6/26/2007 9:13 AM
Page 8
boe_xi_r2_end_to_end_sso.pdf
NOTE
Replace CMSMachineName with the name of your CMS. You may have to change the value of the authenticationDefault to match the authentication type you are using.
4. Restart IIS.
6/26/2007 9:13 AM
Page 9
boe_xi_r2_end_to_end_sso.pdf
Figure 6:
6/26/2007 9:13 AM
Page 10
boe_xi_r2_end_to_end_sso.pdf
4. Close and reopen Internet Explorer for the changes to take effect. 5. Repeat steps 1-3 on each BusinessObjects Enterprise client machine.
NOTE
After following these steps, the next time you access the InfoView URL, you should see Local Internet displayed in the bottom right hand corner of the browser.
Troubleshooting
Looping logon
After setting up Kerberos SSO, you are prompted to enter AD credentials. No matter what you specify in the dialog box, you are repeatedly prompted to logon. This could happening for two reasons: The InfoView URL has not been added as a trusted site on the client machines browser. Refer to the Configuring the Internet Explorer browser on the client section on the previous page for further information. Service principle Name (SPN) has not been registered for HTTP. Refer to Register Service Principle Name (SPN) for information on how to do this.
6/26/2007 9:13 AM
Page 11
boe_xi_r2_end_to_end_sso.pdf
6/26/2007 9:13 AM
Page 12
boe_xi_r2_end_to_end_sso.pdf