Configuring Component Systems for SSO with SAP Logon Tickets

Configuring Component Systems for SSO with SAP Logon Tickets

When a user calls an external application, his or her logon ticket is passed on to the
appropriate application or information system where it is checked to see if it is valid. In order
to work with SAP logon tickets, the external application has to perform three tasks as follows:
...
1. The external system has to make sure that a trusted Portal Server has issued the
ticket.
2. The digital signature in the ticket of the Portal Server needs to be verified. The first two
steps require the digital certificate of the issuing Portal Server.
3. If the ticket is valid, the appropriate user ID contained in it has to be extracted.

In Enterprise Portal import verify.pse and verify.der files from the Portal.

In SAP systems with Release 4.6C or higher you can use transaction
STRUSTSSO2

Go to STRUSTSSO2 and click on import certificate -> Specify the path in which the verify.der file is located and import it.

After importing Choose Add to ACL to add the portal server to the ACL list.

In the dialog box that appears, enter the portal’s system ID and client. By default, the
portal’s system ID is the common name (CN) of the Distinguished Name entered during
installation of the portal. The default client is 000.
If necessary, you can change these default values by changing the properties