Hi
The questions concern SSO/SNC for ‘SAPGUI for Windows’ with 2 different SAP SSO/SNC implementations for Windows and UNIX.
(SAP SSO/SNC will hereafter be referred to as SSO)
Situation
We have for years used SSO for all our Windows based SAP systems (the NTLM flavor) and it works just fine.
Now we plan to configure SSO for all our UNIX based SAP systems using SAP NetWeaver Single Sign-On (the ‘Secure Login Client’ and ‘Secure Login Library’ components).
Requirement
The end-users should be able to access all SAP systems using SSO, that is, typically a mixture of both Windows and UNIX based SAP systems.
Proof-of-concept
We have implemented the SAP NetWeaver Single Sign-On scenario ‘SAPGUI for Windows’ on one of our UNIX based SAP systems and performed a preliminary test.
The test indeed suggests that the current Windows and the new UNIX SSO implementation are conflicting.
When the Secure Login Client is installed on the end-user’s PC the new UNIX SSO implementation works just fine BUT when logging on a Windows based SAP systems with the existing SSO implementation an error message is returned (SNC name could not be decoded).
Questions
The questions are caused by the fact that we will try to avoid a ‘big bang’ roll-out of the SAP NetWeaver Single Sign-On implementation.
Q1: Is a mixed SSO implementation at all possible? (i.e. only the ‘big bang’ roll-out approach is feasible)
Q2: If yes - which rules and conditions apply?
e.g. the optimal solution - if possible - for the Windows based SAP systems would be to dedicate one logon group to support the existing SSO implementation (already in place) and to dedicate another logon group* to support the new SAP NetWeaver Single Sign-On implementation thus only end-users with Secure Login Client installed would be subject to changes.
*) application servers where Secure Login Library is installed and configured
Brgds
Erling