SSO with Kerberos SNC

The following article describes the required steps for setting up Single Sign-On (SSO) with Secure Network Communication (SNC) and Kerberos encryption.

Requirements

• The SAP ABAP application server runs under a Windows operating system.
• The BI client (which calls the extraction) runs under Windows.
• The SAP Kerberos Wrapper Library (gsskrb5) is used as the SNC solution.

"Double Hop" Issue

SNC solution must support the Windows credentials being passed on by Board Connector. Since Active Directory is based on Kerberos, a "Double Hop" issue may occur. Here is a possible solution to the "Double Hop" issue:

For security reasons, Kerberos does not allow credentials to be passed on. But there are Kerberos extensions from Microsoft (S4U extensions) that allow credentials passing on. These extensions are also known as "constrained delegation". Because the Kerberos Wrapper Library uses the Microsoft extensions for Kerberos to work around the "Double Hop" issue, it is only available for Windows. It therefore only works with SAP application servers under Windows and clients under Windows.

Unlike the Kerberos Wrapper Library (gsskrb5) from SAP (according to SAP), SAP's Common Crypto Library does not explicitly support credentials to be passed on. The Kerberos Wrapper Library (gsskrb5) used by multiple customers of Theobald Software.

When using an SNC solution from a third-party vendor, use either the Kerberos Wrapper Library or a corresponding solution of the third-party vendor.

Activation of HTTPS

1. Enable access control protocol HTTPS within the tab Web Server settings.
2. Reference an existing X.509 certificate .
   
3. Click [OK] to confirm .
   

Make sure to check the default ports, e.g., 8197 in Board Connector.

Configuration of Windows AD Service Account

Using SSO with Kerberos SNC, the Board Connector service must run under a dedicated service account.
To do so, follow the steps as outlined in Run the Board Connector Service under a Windows Service Account.

Server Settings

1. Copy the Kerberos Wrapper Library to the file system, e.g., to C:\SNC\gx64krb5.dll of the machine, where the service is running.
2. Place the downloaded .dll file on each machine, where the Designer is running.
3. Open "Computer Management" by entering the following command: compmgmt.msc.
4. Under Local Users and Groups select Groups > Administrators.
5. Click [Add] to add the service account to the local admin group .
   
6. Open "Local Security policy" by entering the following command: secpol.msc.
   
7. Select [Local Policies > User Rights Assignment]:
   • Act as part of the operating system
   • Impersonate a client after authentication

8. Change the registry settings of the server machine:

   Field	Registry Entry
   SubKey	HKEY_LOCAL_MACHINE\SOFTWARE\SAP\gsskrb5
   Entry	ForceIniCredOK
   Type	REG_DWORD
   Value	1

SAP Source Settings

1. In the main menu of the Board Connector Designer, navigate to [Server > Manage Sources]. The window "Source Details" opens.
   
2. Select an existing SAP source and click [Edit] (pencil symbol).
3. Enable the SNC option in the subsection Authentication.
   
4. Enable the checkbox Impersonate authenticated caller (SSO) .
5. Enter the complete path of the Kerberos library in the field SNC library e.g., C:\SNC\gx64krb5.dll .
6. Enter the SPN of the SAP service account in the field Partner name . Use the following notation: p:[SPN]@[Domain-FQDN-Uppercase].
7. Click [Test Connection] to verify your connection settings.
8. Click [OK] to confirm.

SNC Activation in SAP

In SAP, apply the Kerberos SNC settings as described in the SAP Help: Single Sign-On with Microsoft Kerberos SSP.

Related Links

• Documentation: X.509 certificate
• Documentation: Run the Board Connector Service under a Windows Service Account.