SSO with Client Certificates

The following article describes the process of setting up Single-Sign-On (SSO) via Secure Network Communication (SNC) with SAP client certificates. For more information on using SSO with Board Connector (BC), see Documentation: SAP Single-Sign-On.

Requirements

The usage of SSO Certificate requires the correct characteristics of the architecture:

• Implement SAP SSO with X.509 certificates without Secure Login Server, see SAP-Documentation: Authentication Methods without Secure Login Server.
• Implement Microsoft Certificate Store and Active Directory Certificate Templates for SAPGUI/RFC, see Microsoft TechNet: Certificate Template.
• Set up an enrollment agent for Board Connector in AD, see Microsoft TechNet: Establish Restricted Enrollment Agents.
• Install the SAP Secure Login Client on the server that runs Board Connector, see SAP-Documentation: Secure Login Client.
  The Secure Login Client ensures that the correct SNC library is available for SSO Certificate. This library is used to open the SAP connection.
• The Board Connector service must run under a Windows AD Service account, see Run the Board Connector Service under a Windows Service Account.
• Set up access restrictions for the Board Connector Designer and the BC server, see Restrict Access to Windows AD Users (Kerberos Authentication).
  

Process

The following graphic illustrates the process of authentication via SSO Certificate:

1. The user of the BI tool (caller) triggers an extraction by calling the BC webservice of your Xtract product. The caller uses their Active Directory identity to authenticate against the BC webservice via HTTPS and SPNEGO.
2. The BC server checks if a certificate for the caller is available in the Windows Certificate Store. If no certificate is available for the caller, a new certificate is issued by the Windows enrollment agent.
   
   1. The BC server requests the Client certificate from the Windows Certificate Store via the Windows API. If a certificate is available, the process continues with step 3. If no certificate is available steps 2b) to 2e) are executed.
      
   2. The BC server requests an enrollment agent certificate from the Windows Certificate Store via the Windows API. The enrollment agent certificate can be used to issue client certificates.
      
   3. The BC server receives the enrollment agent certificate from the Windows Certificate Store.
      
   4. If the requested certificate from 2a) is not found in the Windows Certificate Store, the BC server enrolls a new client certificate for the caller using the enrollment agent certificate.
      
   5. The Windows Certificate Store receives the new client certificate from the Active Directory Services via MSRPC.
3. The BC server receives the client certificate of the caller from the Windows Certificate Store.
4. The BC server configures the SAP Secure Login Client via the Windows Registry.
5. The Secure Login Client receives the caller's client certificate as specified by the BC server in step 4 from the Windows Certificate Store.
6. The Secure Login Client uses the client certificate of the caller to authenticate the caller's identity via SNC against SAP.
7. The BC server extracts data with the identity and privileges of the caller.
8. The BC server loads the extracted data from 7 to the tool that triggered the extraction.

Setting up SSO and SNC with Client Certificates

Create a new SAP source system in Board Connector to set up SSO with client certificates:

1. Navigate to [Server > Manage Sources] in the main menu of the Designer. The window "Manage Sources" opens.
2. Click [Add] to create a new SAP source.
3. Open the tab General and enter the connection details of your SAP system.
   
4. Open the tab Authentication and activate the option SNC.
   
5. Enter the path to the 64bit version of the SAP Crypto Library in the field SNC library, e.g., C:\Program Files\SAP\FrontEnd\SecureLogin\lib\sapcrypto.dll. The SAP Crypto Library is installed as part of the SAP Secure Login Client.
6. Enter the SNC partner name of the SAP system in the field SNC partner name. This is the same partner name as the SNC name used to set up the SAP GUI.
7. Activate the option Enroll certificate on behalf of caller (Certificate SSO).
   
8. Enter the technical name of the Active Directory Certificate Template used to authenticate SAP users.
9. Enter the thumbprint of the certificate of the enrollment agent. If you don't know the name or thumbprint, consult the IT department that manages the Active Directory Certificate Services.
10. Click [Test Designer Connection] to test your connection settings.
11. Click [OK] to confirm your input.

Related Links

• SAP Help: Secure Network Communications
• SAP Help: Secure Login Client
• SAP Help: Logging on with Secure Login Client Using SNC