Sie sind auf Seite 1von 49

SAP BusinessObjects CSA How-To Guide

Title:

Implementing Client Certificate Authentication in SAP BusinessObjects Planning and Consolidation 10.0, version for NetWeaver
Applies to:
SAP BusinessObjects Planning and Consolidation 10.0, version for NetWeaver, SP1 and higher EPM Add-In, SP3 and higher

Summary
Single Sign On (SSO) is a topic that is often overlooked until well into an implementation. The purpose of this guide is to provide step by step instructions on implementing SSO via client certificates for BPC 10 for NetWeaver. It can be useful for scenarios where a PKI infrastructure already exists as well as for proof of concepts. Author: Daniel Settanni

Company: SAP Labs Created on: 6 October 2011

Author Bio
Daniel Settanni has worked SAP Labs in the EPM Customer Solution Adoption (CSA) for the last four years. He specializes in SAP BusinessObjects Planning and Consolidation, both the Microsoft and NetWeaver releases.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Error! No text of specified style in document.

Table of Contents
Prerequisites ....................................................................................................................................................... 3 Overview ............................................................................................................................................................. 4 Creating the Certificates ..................................................................................................................................... 5 Creating and exporting the Certificate Authority certificate in XCA ................................................................ 5 Creating and exporting the client X.509 certificate ......................................................................................... 9 Creating and exporting the SAP NetWeaver Web Application Server certificate ......................................... 16 Configuring BW ................................................................................................................................................. 20 Review required parameters to enable client certification authentication ..................................................... 20 Ensure HTTPS is enabled............................................................................................................................. 20 Importing the Certificate Authority certificate ................................................................................................ 23 Adding the X.509 certification to the ACL ..................................................................................................... 26 Mapping the X.509 client certificate to an ABAP (BPC) user ....................................................................... 29 Configuring the PC ........................................................................................................................................... 32 Setup the WAS server certificate as a Trusted Root CA on the PC ............................................................. 32 Setup the CA certificate as a Trusted Root CA on the PC ........................................................................... 37 Setup the X.509 client certificate as a Personal certificate on the PC .......................................................... 39 Test Cases ........................................................................................................................................................ 43 Logging into the BPC Web Client ................................................................................................................. 43 Logging in with the EPM Add-In .................................................................................................................... 44 Related Content ................................................................................................................................................ 48 Copyright........................................................................................................................................................... 49

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Error! No text of specified style in document.

Prerequisites
This How-To Guide depends on: A Public Key Infrastructure (PKI) or the XCA (X Certificate and Key Management) utility o The XCA utility is an open source application intended for creating and managing X.509 certificates, certificate requests, RSA, DSA and EC private keys, Smartcards and CRLs and is used in this guide because of its ease of installation and use. The XCA utility can be downloaded from here: http://xca.sourceforge.net/ o The XCA utility can be installed on any system if you choose to use it.

Any PKI infrastructure will do, and the use of the XCA utility in this guide is not an endorsement of it above any other solution. The production PKI infrastructure should be selected by a companys network security team.

SAP NetWeaver, version 7.3 (ABAP stack) SAP BusinessObjects Planning and Consolidation 10.0, version for NetWeaver (BPC), version 10.0 SP2+ EPM Add-In, SP3+ A method to resolve the Fully Qualified Domain Name of the SAP NetWeaver Web Application Server. o o This can either be via DNS or a hosts file on the client PC. The FQDN (Fully Qualified Domain Name) must match the common name on the certificate assigned to the SSL (Secure Sockets Layer) server Standard PSE.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Error! No text of specified style in document.

Overview
Single Sign On (SSO) is a topic that is often overlooked until well into an implementation. The purpose of this guide is to provide step by step instructions on implementing SSO via client certificates for BPC 10 for NetWeaver. It can be useful for scenarios where a PKI infrastructure already exists as well as for proof of concepts.
Note: This guide provides details on creating a self signed Certificate Authority to sign the X.509 certificates enabling client certification authentication using the XCA application. Customers with an existing PKI infrastructure can skip these steps and use certificates generated by their own CA.

Note: This guide is not intended to be instructions on how to setup and maintain the PKI infrastructure for a company and is for demonstration purposes only.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Error! No text of specified style in document.

Creating the Certificates


This section covers: Creating and exporting the Certificate Authority in XCA Creating and exporting the client X.509 certificate Creating and exporting the SAP NetWeaver Web Application Server certificate

Note: This section is optional if you have a preexisting PKI infrastructure. In that case, generate and export the required certificates according to your PKIs instructions.

Note: This section requires that you have downloaded and installed XCA (see Prerequisite section).

Creating and exporting the Certificate Authority certificate in XCA 1. Launch XCA. 2. Create a new database by selecting File > New Database. Save the database somewhere safe, and assign an appropriate password.

3. Select the Certificates tab and click the New Certificate button.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Error! No text of specified style in document.

4. On the Source tab select [default] CA as the template and click the Apply All button.

5. Select the Subject tab and enter the requested information, then click Generate a new Key

Note: This commonName will be displayed as the issuer for our client X.509 certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Error! No text of specified style in document.

6. Select the Keytype and Keysize. Next click Create.

7. Click OK to create the certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

Error! No text of specified style in document.

8. On the Certificates tab, select the newly created CA certificate and click Export.

9. Verify the file path, select DER as the export format then click OK.

Note: The resulting file will contain the public key of the Certificate Authority.

Note: The export format determines the file type (binary or base64) as well as the contents (public key, private key or both).

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

Error! No text of specified style in document.

Creating and exporting the client X.509 certificate 1. Launch XCA and open the database created in the previous section. 2. Navigate to the Certificates tab, and click New Certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

Error! No text of specified style in document.

3. Check Use this certificate for signing then select the CA certificate created in the last section from the drop down then select [default] HTTPS_client as the template and click the Apply All button.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

Error! No text of specified style in document.

4. Select the Subject tab and enter the requested information, then click Generate a new Key

5. Select the Keytype and Keysize. Next click Create.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

Error! No text of specified style in document.

6. Click OK to create the certificate.

Note: X.509 client certificates need to be created for each unique user. We will only create one in this guide, but the process from creating additional client certificates is identical, except the commonName attribute generally maps to the users real name or logon id.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

Error! No text of specified style in document.

7. On the Certificates tab, select the newly created client HTTPS certificate and click Export.

8. Verify the file path, select DER as the export format then click OK.

Note: The resulting file will contain the public key of the HTTPS client certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 13

Error! No text of specified style in document.

9. On the Certificates tab, select the newly created client HTTPS certificate and click Export again.

10. Verify the file path, select PKCS #12 with Certificate chain as the export format then click OK.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 14

Error! No text of specified style in document.

11. Enter a password to encrypt this certificate then click OK.

Note: The resulting file will contain the public and private key pair for the HTTPS client certificate. In a production environment this file is extremely sensitive and should be protected.

Note: At this point you should have exported three certificates: The CA public key The HTTPS clients public key The HTTPS clients public/private key pair

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 15

Error! No text of specified style in document.

Creating and exporting the SAP NetWeaver Web Application Server certificate In this section we will ensure that your SAP NetWeaver Web Application Server has an SSL certificate assigned. If it doesnt, we will create one using t-code STRUST. 1. Log into the BPC 10 for NetWeaver ABAP server via SAPGUI. 1. Go to t-code STRUST 2. Review the status of the SSL server Standard PSE. If you do not see a red X next to it, continue on to step 7 to export the certificate. Otherwise continue with step 4 to create the PSE.

3. If you see a red X, then the PSE has not been created yet. Right click on the SSL server Standard entry and select Create.

4. Accept the default values for the PSE and click the green checkmark.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 16

Error! No text of specified style in document.

5. Accept the default values for the SSL Server and click the green checkmark.

6. Expand the SSL server Standard PSE and double click on the node below.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 17

Error! No text of specified style in document.

7. Double click on the certificate DN in the Own Certificate section.

8. Click the Export Certificate button in the Certificate section.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 18

Error! No text of specified style in document.

9. Enter the appropriate file path, select Binary as the file format and click the green checkmark.

Note: The certificate we just exported contains the Public Key for the NetWeaver instances Web Application Server. We will import or trust this certificate on the client system a little later on.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 19

Error! No text of specified style in document.

Configuring BW
In this section we will: Review required parameters to enable client certification authentication Ensure HTTPS is enabled Import the Certificate Authority certificate Add the X.509 certification to the ACL Map the X.509 certificate to an ABAP (BPC) user

Review required parameters to enable client certification authentication The following parameter must be set to enable client certificate authentication: login/accept_sso2_ticket = 1 login/create_sso2_ticket = 2 login/ticket_expiration_time = 8 o Expiration time can vary depending on your security policy.

These parameters can be set via t-code RZ10. Consult with your BASIS team to implement these parameters.
Note: You may have to restart your SAP NetWeaver server to activate these changes.

Ensure HTTPS is enabled 2. Log into the BPC 10 for NetWeaver ABAP server via SAPGUI. 1. Go to t-code SMICM and click the Services icon.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 20

Error! No text of specified style in document.

2. Check the table to see if HTTPS is Active. If it is you can continue to the next section. If not, continue with the next step to activate it.

Note: If there is no line here you are missing an ICM Profile Parameter. Please see help site for possible ICM Profile Parameter values: http://help.sap.com/saphelp_nw73/helpdata/en/48/63bcaff29407bee10000000a42189d/frameset.htm

Note: Take note of the Port for HTTPS as you will need to reference it in the URL if it is not the default (443).

3. Check the HTTPS row then click Service > Activate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 21

Error! No text of specified style in document.

4. HTTPS should now be active.

Note: You can test HTTPS by navigating to the following URL in Internet Explorer: https://hostname:port/sap/bpc/web The hostname and port can be obtained from t-code SMICM (see step 3 and 5 from this section). Note: You may also get an SSL error if you test the site at this point. Thats OK; well fix that in a subsequent section.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 22

Error! No text of specified style in document.

Importing the Certificate Authority certificate In this section we will import our Certificate Authority into the SSL server Standard PSEs root certificate database. 1. Log into the BPC 10 for NetWeaver ABAP server via SAPGUI. 2. Go to t-code STRUST. 3. Expand the SSL server Standard PSE and double click on the node below.

4. Click the Import certificate button in the Certificate section.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 23

Error! No text of specified style in document.

5. Browse to the Certificate Authorities public key that we exported earlier, select the Binary file format and click the green checkmark.

6. Click the Add to Certificate List button.

Note: This first step makes the PSE (Personal Security Environment) aware of the CA certificate, but does not mark it as a trusted root certificate authority. In other words, the PSE will not yet trust certificates signed by our CA cert. We will make in a trusted root certificate in the next few steps.

7. Click the Export button in the Certificate section.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 24

Error! No text of specified style in document.

8. Enter ZZSSOCA as the Trust Center, select Root CA as the Category, enter a description and click the green checkmark.

Note: The trust center can be named something other than ZZSSOCA as long as the name begins with ZZ.

9. Click the Save button.

Note: Our CA certificate is now trusted as a Root Certificate Authority.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 25

Error! No text of specified style in document.

Adding the X.509 certification to the ACL In this section we will add the HTTPS client public key we exported earlier to the SSL server Standard PSE so the WAS can recognize and authenticate client requests. 1. Log into the BPC 10 for NetWeaver ABAP server via SAPGUI. 2. Go to t-code STRUSTSSO2. 3. Expand the SSL server Standard PSE and double click on the node below.

4. Click the Import certificate button in the Certificates section.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 26

Error! No text of specified style in document.

5. Browse to the HTTPS client public key that we exported earlier, select the Binary file format and click the green checkmark.

Note: Make sure you select the CER file and not the P12 file.

6. Click the Add to ACL button.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 27

Error! No text of specified style in document.

7. Enter the System ID and Client then click the green checkmark.

8. The certificate will now appear in the Logon Ticket section.

9. Click the Save button.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 28

Error! No text of specified style in document.

Mapping the X.509 client certificate to an ABAP (BPC) user In this section we will map the X.509 client certificate to an ABAP/BPC user. This step allows the WAS to know who to execute transactions as when the X.509 certificate is supplied. 1. Log into the BPC 10 for NetWeaver ABAP server via SAPGUI. 2. Go to t-code SM30 and maintain view VUSREXTID.

3. Enter DN as the work area and click the green checkmark.

4. Click New Entries.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 29

Error! No text of specified style in document.

5. Click the Import button next to the External ID textbox.

6. It is safe to disregard the informational message that appears click the green checkmark.

7. Select the X.509 client certificate and click Open.

Note: This reads the X.509 certificates distinguished name or DN from the certificate directly as well as the issuer which helps to avoid typos, etc.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 30

Error! No text of specified style in document.

8. Enter the name of the ABAP user that maps to this certificate in the User textbox, enable the Activated checkbox and click Save.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 31

Error! No text of specified style in document.

Configuring the PC
At this point we have: 1. 2. 3. 4. Created CA and X.509 client certificates Created (or verified) the WAS SSL certificate Ensured the NetWeaver system trusted the CA and X.509 client certificates Mapped the X.509 client cert to an ABAP user

But we are still missing a couple pieces. The client PC doesnt trust the WAS server or CAs certificates and doesnt know to use the X.509 client certificate. This section ties up those loose ends. Setup the WAS server certificate as a Trusted Root CA on the PC 1. Log onto the PC that has the EPM Add-In installed 2. Go to Start > Run and type mmc. Click OK.

3. Click File > Add/Remove Snap-in.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 32

Error! No text of specified style in document.

4. Select the Certificates snap-in and click Add.

5. Select My User Account and click Finish.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 33

Error! No text of specified style in document.

6. Click OK.

7. Expand Certificates. Right click on Trusted Root Certification Authorities, select All Tasks > Import.

8. Click Next on the Welcome screen.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 34

Error! No text of specified style in document.

9. Enter the path and filename of the SSL certificate we exported from STRUST. Click Next.

10. Ensure the certificate is being imported into the Trusted Root Certification Authorities store. Click Next.

11. Click Finish.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 35

Error! No text of specified style in document.

12. Click Yes when asked if you are sure you want to install the certificate.

Note: We had to import the WAS servers public key into the Trusted Root Certification Authority store because it is a self signed certificate.

Note: Leave the MMC open for the next two sessions.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 36

Error! No text of specified style in document.

Setup the CA certificate as a Trusted Root CA on the PC


Note: If you closed the Certificate snap-in of the MMC, go back through steps 1 through 6 of the previous exercise to reopen it.

1. Expand Certificates. Right click on Trusted Root Certification Authorities, select All Tasks > Import.

2. Click Next on the Welcome screen. 3. Enter the path and filename of the CA certificate. Click Next.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 37

Error! No text of specified style in document.

4. Ensure the certificate is being imported into the Trusted Root Certification Authorities store. Click Next.

5. Click Finish. 6. Click Yes when asked if you are sure you want to install the certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 38

Error! No text of specified style in document.

Setup the X.509 client certificate as a Personal certificate on the PC


Note: If you closed the Certificate snap-in of the MMC, go back through steps 1 through 6 of the previous exercise to reopen it.

1. Expand Certificates. Right click on Personal, select All Tasks > Import.

2. Click Next on the Welcome screen. 3. Click the Browse button to the right of the filename textbox

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 39

Error! No text of specified style in document.

4. Change the file type to Personal Information Exchange (*.pfx; *.p12) and select the X.509 client certificate. Click Open.

5. Click Next. 6. Enter the password you set when exporting the private key for the X.509 certificate, and optionally mark the key as exportable. Click Next.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 40

Error! No text of specified style in document.

7. Ensure the certificate is being imported into the Personal store. Click Next.

8. Click Finish. 9. Click Ok when the message The import was successful is displayed.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 41

Error! No text of specified style in document.

Note: You can also test the validity of the X.509 certificate by navigating to Certificates > Personal > Certificates and viewing the properties on the newly imported certificate. There are two key items to look for: the first is to make sure you have the private key installed. This is visible on the General tab. The second is to make sure the Certificate Status is OK in the Certification Path tab.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 42

Error! No text of specified style in document.

Test Cases
In this section we will use the client certificate to login to: The BPC web client The EPM Add-In

Logging into the BPC Web Client 1. Launch https://server:port/sap/bpc/web in Internet Explorer 2. You should either be logged in automatically, or be prompted to select a certificate (see below) depending on your security settings.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 43

Error! No text of specified style in document.

Logging in with the EPM Add-In 1. Launch Microsoft Excel. 2. Select the EPM ribbon and click on Log On.

3. Click on the button to create a new connection.

4. Click Create. 5. Select the Planning and Consolidation connection type, enter a connection name, enter the server URL (remember to use HTTPS), select Version for SAP NetWeaver and check Client Certificate. Click Choose Certificate.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 44

Error! No text of specified style in document.

6. Select the certificate and click OK.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 45

Error! No text of specified style in document.

7. Click Connect.

8. The Environments and Models will be detected without having to enter credentials. Select a valid Environment and Model and click OK.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 46

Error! No text of specified style in document.

9. Highlight the newly created connection and click OK.

10. Click Logon. You will be logged in without being prompted for credentials.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 47

Error! No text of specified style in document.

Related Content
BPC 10 for NetWeaver Authentication Scenarios Blog SBOP PC 10 for NetWeaver Security Guide SAP NetWeaver 7.3 Security Guide > User Authentication and SSO

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 48

Error! No text of specified style in document.

Copyright
Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 49