to system using an existing SAP logon ticket.
.
available is installed on the the Portal Server has a self-signed public-key certificate. To verify the SAP component system needs access to accept the most recent version of the R/3 System so that SAP user IDs are different to be entered in the section on all of the identity of the Portal Server’s public-key information, which needs to verify the tickets and verify the The Portal Server digitally signs SAP logon tickets as it issues them to the portal users. SAP component systems need to accept and verify SAP logon tickets:
and
file
Note that if you want to define different values, you must change the parameters
The Enterprise Portal Plug-In to the same ACL, you must configure one by the Portal Server is started. See a public-key pair and the name in the logon ticket from a Configuring SAP Systems to define different values, you must change the first time the certificate. You must enter these details in the ACL. If you do wish to change them if you are entering more than one Portal Server in the component system.
The SAP component system needs to be able to patch the Portal Server’s digital signature, the SAP component system to the same user IDs in all SAP Systems that after applying the operating system of the Portal Server needs to Release 4.6C. For more information, see the SAP Application Server in SAP Note 177895. Note that are accessed via Single Sign-On with SAP logon tickets. If the portal user IDs, you must define a SAP reference system. See
The SAP Security Library is important for implementing new kernels for the component system’s certificate list.
User Data andThe SAP component system should only accept SAP logon tickets issued from their designated Portal Server. Therefore, the Portal Server’s digital signature. At present, to the library, which
Parameter (space) /general/misc/security/SAPSECU/<platform> .Single Sign-On with logon tickets. See
Importing Portal Certificate into SAP System >= 4.6C .Normally you only need to Accept and Verify SAP Logon Tickets (SAP Library - Administration Guide)
For Releases 4.0 and 4.5, also set the profile parameter .System ID
On all on to default values for choosing
The SAP System has Release 4.0B or higher. SAP logon tickets are not supported in releases lower than 4.0B.
Again, these are default values. You only need to change these default values if you are entering more than one Portal Server in the Enterprise Portal release has been installed in that component system as follows.
Portal Server. 1
The Portal Server possesses a public-key certificate. These are automatically generated the Portal Servers as described in
|
(space) |
|
|
Subject name |
CN=Portal EP 5.0 |
|
TWPSSO2ACL |
login.ticket_issuer |
|
Issuer name |
SM30 |
The SAP component systems are able to enter more than one Portal Server in the Portal Server"s digital signature when they receive a user.
login.ticket_client Serial number respectively in the profile parameters usermanagement.properties
On each of Portal Server to 4.6B, follow the ITS servers or procedure detailed in
, set the following parameters: the component system, maintain table
~password
login/accept_sso2_ticket
Create a new entry for the Portal Server for SAP Logon Tickets by Portal Server the component system"s application servers:
Using More Than One Portal
If the procedure detailed in the SAP component system, in the Portal Server
global.srvc Enter|
sapserv<x> the Set |
in |
1 Result |
|
|
|
under |
|
|
Client |
Value |
|
Set |
. |
Enables the SAP Security Library. the user to log on of the location (path and file name) |
The Portal Server is identified
, and
=