Show TOC

Implementing AuthenticationLocate this document in the navigation structure

SAP NetWeaver AS ABAP provides the user authentication and single sign-on (SSO) functions for SAP Gateway, however, to enable user authentication and SSO, you must configure GWM to use the implemented authentication.


Note If configuration is maintained in both the ADM and App.config files, the configuration maintained in the ADM is given preference. If ADM configuration is not maintained for the logged-in user, then configuration in the App.config file is consumed.

Developer Testing


GWM supports the use of the following authentication mechanisms:

  • Basic
  • SAML 2.0
  • X.509 Certificate
  • Kerberos
  • OAuth 2.0

    The GWM: Visual Studio Add-in currently supports only Basic authentication with SMP.

    For Visual Studio integrated with Azure, OAuth 2.0 is the default authentication mechanism.

User Testing


To roll out the security mechanism to the users follow these steps:
  1. Open the Group Policy Management Editor in the domain controller from where the Admin wishes to roll-out the security configurations to all the end users.
  2. Open the group policy object for the GWM Outlook Project
  3. Change the Value of SSO to X509, or SAML20 or Kerberos accordingly to use X.509, SAML, or Kerberos authentication mechanism in the settings section and save the configuration.
    Note GWM Visual Studio Add-In does not support Basic authentication for end users. If you want to use the Basic authentication option for end users, then you must extend the generated code to handle the HTTP 401 response in Microsoft Outlook to enable the end users to enter the user name and password.
  4. Log on to a client machine that is connected to the domain and log in with a user for whom the policy is applicable.
  5. Open the command prompt and run the GPUPDATE/force command to force synchronize the policy, in case it is not already synchronized.