Sap Single Sign On Certificate



Symptom

You have configured SAP Single Sign-On based on X.509 Certificates and the following error happens when logging on to SAP GUI:

GSS-API(maj): Miscellaneous failure
GSS-API(min): A2210223: Server does not trust my certificate path
target='SNC Name'

SAP Single Sign-On This document describes how to implement SPNEGO based Single Sign-On using Secure Login Server X.509 Client Certificates and to achieve end-to-end single sign-on across your corporate landscape. SAP Single Sign-On 2.0 – What’s New in Support Package 03. Two-Factor Authentication with SAP Authenticator. SSO for SAP GUI for Java on Mac OS X. RFID-Based User Identification. Hardware Security Module Support.


Read more...

Environment

Product

SAP Single Sign-On 2.0 ; SAP Single Sign-On 3.0

Keywords

Sap Single Sign On Certificate

PKI, public key infrastructure, Secure Login Client, Secure Login Server. , KBA , BC-IAM-SSO-SL , Secure Login , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.

Configure the SSO (Single sign on) for Portal

How to configure the SSO (Single sign on) for Portal? What are the steps needs to be taken?

By: Kamakshi

Single Sign On with Portal to SAP Backend Systems

Single Sign On (SSO) is good documented in the SAP world. This guide to give you a complete working example of how you can enable SSO in your environment.

Step 1 - Setting the logon method as Single Sign on

1.1 Log in to your Portal as a System Administrator.

1.2 Choose System Administration --> System Configuration --> System Landscape

1.3 Find the system you want to assign Single Sign on to and open it

1.4 Choose User Management as Property Category

1.5 Set Logon Method to SAPLOGONTICKET

Sap single sign on certificate printable

What we have done now is to set the system you want to use as a Single Sign On logon method. Do this to each system you want to connect.

Step 2 - Create a Portal Certificate

1.1 Log in to the Visual Administrator

1.2 Choose Server --> Services --> KeyStorage --> TicketKeystore

1.3 Delete SAPLogonTicketKeypair-cert and SAPLogonTicketKeypair

1.4 Choose Create (Create button in the Entry field) and
type in the following information:
a. mark Store Certificate
b. Common Name: Your <SID> (just example)
c. Entry Name: SAPLogonTicketKeypair
d. Store Certificate: Mark it
e. Key Length: 1024
f. Algorithm: DSA
g. Press Generate

Now you will have two entries in the TicketKeyStore:

SAPLogonTicketKeypair
SAPLogonTicketKeypair-cert

Step 3 - Export the Portal certificate

3.1 Choose Server --> Services --> KeyStorage --> TicketKeystore

3.2 Choose SAPLogonTicketKeypair-cert and press Export (Export button in the Entry field)

a. Fill in a name of the Certificate
To keep track of your certificate, call it the SID of the Portal

b. Choose either X.509 or Base64 Encoded Format

Step 4 - Import the Portal certificate to the Backend System

4.1 Log in to the Backend System
In my example, I log in to ERP 2004

4.2 Run transaction STRUSTSSO2

4.3 Press Import Certificate (Button in the Certificate field)

a. Open the generated certificate from step 3 with the right file format that you choosed in step 3.4

4.5 Press Add to Certificate List button (Button in the Certificate field)

4.6 Press Add to ACL button (Button in the Certificate field)

a. Enter the <SID> of your Portal

b. Enter Client 000

4.7 Press Save

Step 5 - Export the Backend certificate to your Portal

5.1 You are still in the transaction STRUSTSSO2. Doubleclick the Owner Certificate and choose Export and store in on the file system

5.2 Log into Visual Administrator
Choose Server --> Services --> KeyStorage --> TicketKeystore and press Load and choose the Certificate

5.3 Set the Backend System as 'ACL' in the Portal
Choose Server --> Services --> Security --> Provider --> Ticket

Choose the Authentication tab and add the following on the com.sap.security.core.server.jass.EvaluateTicketLoginModule:

trustedsys<Number>=<ABAP_SID>, <CLIENT> (for example, ABA, 200)

trustediss<Number>=<ISSUER_DISTINGUISHED_NAME> (for example, CN= ABA)

trusteddn<Number>=<SUBJECT_DISTINGUISHED_NAME> (for example, CN=ABA)

You have set up a trusted relationship between your portal and the backend system. To do so with several system, run this guide again from step 4

Get help for your Basis problems
Do you have a SAP Basis Question?

SAP Basis Admin Books
SAP System Administration, Security, Authorization, ALE, Performance Tuning Reference Books

SAP Basis Tips
SAP BC Tips and Basis Components Discussion Forum

Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

Sap Single Sign On License

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity. Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.