Single-Sign on in your SAP Landscape has changed with the gradual introduction of the SAP Web AS Java for use with each of your applications. With the delivery of SAP’s most widely used J2EE application, the SAP NetWeaver Portal; and the use of the Web AS Java for many other Java applications being delivered by SAP, there is an increasing need for the Java Engines within your enterprise to be enabled for Single-Sign On.
As the basis for any of the SAP System Trust relationship, we will need to take the Public key from each of the SAP Systems and exchange them, to allow non-repudiation. This step allows each of the Portal system to be certain that the SAP Logon ticket it receives was really created by the System it has been told to trust.
Enjoy!
