Skip to Content


You must be Logged on to comment or reply to a post.

  1. Nelis Lamprecht

    Hello Regine,

    Thank you for the information. Please can you confirm something for me…

    With SLWC 3.0 are you saying clients no longer need to belong to a Microsoft AD domain and use Kerberos ? They can now simply use, as is with our case, Microsoft ADFS for SAML 2.0 Web SSO authentication and SLWC 3.0 can issue a x.509 certificate based on the SAML assertion to enable clients to also access SAP GUI without re-authenticating ?

    Thanks & regards,


      1. Nelis Lamprecht

        Thanks for the confirmation Marcus. I’ve been waiting patiently for a solution where a Microsoft AD domain is no longer a requirement for SSO using the SAP GUI.

  2. Uwe Klein


    I tried to download the SLC 3.0 from the marketplace. Before downloading I get a info that SLC 3.0 is classified as ECCN 5D002 (Export Restrictions). But when I read the documentation in I see that only Secure Login Web Client is is classified as ECCN 5D002.

    If I don’t install/use the SLCW 3.0 do I also have to take care about ECCN 5D002 restrictions ??





  3. Christian Cohrs

    Hi Uwe,

    please download the Secure Login Client by searching for the product SAP Single Sign-On and then accessing the comprised components. In the context of the product, the SLC does not have an ECCN. The documentation refers to the old SLWC version that was based on a Java app and the download of binary components. As of version 3.0, the recommend approach is to use a locally installed SLC. In that case there is no download anymore.

    Best regards,


  4. Chandrakanth Angannagari

    Hi, It is not possible to directily establish SAPGUI based SSO using ADFS . But it is indirectly possible using the SWLC with Secure Login Server and using the post authentication methods of SWLC to enable SAPGUI based SSO using ADFS (which serves as SAML Identity provider) .


    Is this statement correct?


Leave a Reply