Using old Kerberos gsskrb5.dll and new sapcrypto.dll in parallel for different systems

[former_member361867]

Dear SAP-SSO experts,

We are still using the old kerberos-dll "gsskrb5.dll" for SSO in SAP-GUI in our Windows-Environment.

We are going to change are SSO scenario to sapcrypto.dll step by step in our landscape.

There are 2 Environment-Parameters in my front end PCs pointing to the relevant dlls:

SNC_LIB=C:\Program Files (x86)\SAP\SNC\gsskrb5.dll

SNC_LIB_64=C:\Program Files (x86)\SAP\SNC\gsskrb5.dll

I can set these variables either for the old-dll (gsskrb5.dll) or for the new one (sapcrypto.dll) ! So I have to change the SSO-solution for all my sap-systems at once!

Is there any solution to make it possible, that some SAP-systems be able to use the old solution and some others use the new one (on same Front end!)

Thanks and Best Regards

Armin

[Christian_Cohrs]

Hi,

we created a blog some time ago, to explain the migration process. This might be helpful here.

https://blogs.sap.com/2015/04/15/snc-product-migration-now-is-the-time/

Best regards,
Christian

[tim_alsop · Accepted solution]

I assume you are aware that you have to buy a SAP SSO license if you want to use the SAP Cryptolib for SNC SSO. You can also buy a license for a third party SNC SSO product if you want to consider an alternative to SAP SSO.

Anyway, you need to set SNC_LIB_2 and SNC_LIB_64_2 and then both libraries can be used by SAP GUI depending on which system the user logs onto.

[former_member361867 · Accepted solution]

Thank you very much. I will try the SNC_LIB_2 and SNC_LIB_64_2 variables.

Thanks and Best Regards

Armin

[former_member361867 · Accepted solution]

Thank you very much! This solution works very well !