Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Single sign-on (SSO)

With single sign-on (SSO), you can minimize the number of times a user has to log on to access apps and websites.

When you set up SAP Connector as a data source in Qlik Sense, you can configure SAP Connector for SSO. You store the Qlik Sense user credentials and define a trusted relationship so that the system passes the Qlik Sense credentials to the connector.

Requirements

The following prerequisites must be set up in the SAP environment before configuring SSO:

  • The SAP BW platform must be configured for Secure Network Communication (SNC). For more information on SNC, see Secure network communication.

  • The version of SAP Cryptolib file type on the SAP BW platform must be compatible with the version of the SAP Cryptolib on the Qlik Sense server.

    The files needed can be found on the SAP help portal:

    • SAPCAR32-bit version for unpacking files.
    • SAPCRYPTOLIB 64-bit version, in a build that is suitable for the servers where SAP BW and Qlik Sense are deployed.
  • A user account.
Information noteConfirm that you have all the necessary SAP licenses for using server-side trust with SAPCRYPTOLIB.

Server-side trust overview

The server-side trust path for SSO with Qlik Sense and SAP is as follows:

  1. A user in browser authenticates with their credentials.
  2. Their credentials are sent to Qlik Sense, which refers against the installed cryptographic credentials.
  3. Qlik Sense then impersonates the user when connecting to SAP BW, using the credentials to establish server-side trust.
Illustration of Server-side trust path described above

Setup on the Qlik server

Three environment variables need to be set on the Qlik Sense server: SNC_LIB, SECUDIR and QLIK_SNC_LIB.

  • 32-bit SAP Cryptolib must be installed on the Qlik Sense server. Set the environment variables SNC_LIB and SECUDIR.

    Do the following:

    1. Copy the files SAPCAR_<Version>.EXE and SAPCRYPTOLIBP_<Version>.SAR to an empty temporary directory.

    2. Run the command: SAPCAR_<Version>.EXE –xvf SAPCRYPTOLIBP_<Version>.SAR

    3. Copy the extracted files to the location you intend to use as the SNC_LIB directory. Usually this is C:\Program Files\SAP\Crypto.

    4. Create a system environment variable named SNC_LIB that points at the file sapcrypto.dll that you copied to this directory. This could be C:\Program Files\SAP\Crypto\sapcrypto.dll.

    5. Create a system environment variable named SECUDIR that points at a sub directory for the SNC_LIB named sec. This could be C:\Program Files\SAP\Crypto\sec. Move the file sapgenpse.exe from the SNC_LIB folder to the SECUDIR folder.

  • 64-bit SAP Cryptolib must be installed on the Qlik Sense server.

    Extract the 64-bit SAPCRYPTOLIBP_<Version>.SAR file with SAPCAR to an empty folder using the command SAPCAR_<Version>.EXE –xvf SAPCRYPTOLIBP_<Version>.SAR.

    Move the files to an appropriate folder. This could be C:\Program Files\SAP\Crypto64. Create the environment variable QLIK_SNC_LIB and point it to the 64 bit sapcrypto.dll. This could be C:\Program Files\SAP\Crypto64\sapcrypto.dll.

Establishing server-side trust

To establish server-side trust you must do the following.

  • Generate a new Personal Security Environment using sapgenpse.
  • Import the Qlik Sense PSE certificate.
  • Export the BW Instance Certificate.
  • Set up access control for the Qlik Sense server identity.
  • Import the BW Instance Certificate on the Qlik Sense server.
  • Configure PSE access on the Qlik Sense server.

Generating a new Personal Security Environment (PSE)

To generate a new PSE you will need to execute sapgenpse on the Qlik Sense server, using the 32-bit SAP Cryptolib. Make sure that you create the PSE with the same user that is set to run the Qlik Sense services.

Do the following:

  1. Log on to the server using the same user that is set to run the Qlik Sense services.

  2. Choose a PIN. Keep a record of the PIN because it will be needed in the following steps.

  3. Navigate to the SECUDIR directory. Τhis could be C:\Program Files\SAP\Crypto\sec.

  4. Execute sapgenpse.exe with a command line tool using the following commands:

    • sapgenpse.exe gen_pse -v -p <NameOfQlikUser>.pse
    • Enter your chosen PIN twice. Ignore the warning.
    • Enter the Distinguished Name of PSE owner as defined in Active Directory or similar: CN=<NameOfQlikUser>,OU=<OrganizationalUnit>,DC=<DomainComponent>

      Example:CN=rd-sapssotest,OU=R&D,DC=RDLund,DC=qliktech,DC=com

  5. Verify that the SECUDIR directory contains a .pse file.

  6. Export the PSE’s certificate with the following command:

    • sapgenpse.exe export_own_cert –v –p <NameOfQlikUser>.pse –o < NameOfQlikUser>.crt

  7. Verify that the SECUDIR directory contains a .crt file.

Importing the PSE certificate

You need to import the Qlik Sense PSE certificate in the SAP BW instance using STRUST.

Do the following:

  1. Log into the BW instance and start Transaction STRUST.

  2. Double-click the entry under SNC_SAPCryptolib in the left pane.

  3. Verify that the Own Certificate subject value changes to the Distinguished Name of the BW Instance Identity. For example, CN=SAPServiceH7R.
  4. Double-click the Own Certificate value to view details in the Certificate section of the Trust Manager: Change screen.

  5. Import the Qlik Sense server .crt file:
    • Click the eyeglass button in the upper left corner to enable editing.
    • Click Import certificateat the bottom left corner of the certificate section.
    • In the Import Certificate dialog, browse to your SECUDIR directory, select the .crt file, and select the green check mark.
    • Click Add to Certificate List at the bottom of the certificate section.
    • Verify that the certificate appears in the Certificate List.
  6. Click Save.

Exporting the BW Instance Certificate

You need to export the BW Instance Certificate using STRUST.

Do the following:

  1. Double-click the entry under SNC SAPCryptolib in the left pane.
  2. Double-click the Own Certificate subject value. For example, CN= SAPServiceH7R.
  3. In the certificate section, verify that the subject value matches the Own Certificate value.
  4. Export <BWInst.crt>:
    • Click the eyeglass icon in the upper left corner to enable editing.
    • Click the Export certificate button in bottom left corner of the certificate section.
    • In the export dialog, navigate to the SECUDIR directory and enter <BWInst.crt> in the File name box.
    • Specify the file format Base64 and click the green check button.
    • Verify that the certificate now appears in the SECUDIR directory.
  5. Exit transaction STRUST.

Setting up access control for the Qlik Sense server identity

You must set up access control for the Qlik Sense server identity in SNC0.

Do the following:

  1. Start transaction SNC0.
  2. Select New Entries.
  3. In the System ID box, provide a value for the Qlik Sense server identity.
  4. Click the pencil button on the SNC Name box and enter the SNC Name of the Qlik Sense identity. This value should be p: followed by the Distinguished Name of the Qlik Sense server identity. This could be p:CN=<NameOfQlikUser>,OU=<OrganizationalUnit>,DC=<DomainComponent>.
  5. Click the green check mark. You should now see a green check mark next to Canonical Name Determined.
  6. Check the following boxes:
    • Entry for RFC activated
    • Entry for CPIC activated
    • Entry for certificate activated
    • Entry for ext. ID activated
  7. Click Save.
  8. Exit transaction SNC0.

Importing the BW Instance Certificate on the Qlik Sense server

In the SECUDIR directory, execute the following command: ..\sapgenpse.exe maintain_pk -v -a <BWInst.crt> -p <SenseSrv.pse>

Configuring PSE access on the Qlik Sense server.

You must also configure PSE access on the Qlik Sense server.

Do the following:

  1. Execute the following command: ..\sapgenpse.exe seclogin -p <SenseSrv.pse>
  2. Verify that the directory contains a cred_v2 file.
  3. List the contents of the PSE by executing the following command:

    ..\sapgenpse.exe maintain_pk -l

  4. The PKList should have at least one entry with Subject and Issuer values that match the Distinguished Name of the BW Instance Identity.

User mapping in SAP

Do the following:

  1. Start transaction SM30.
  2. Select the view VUSREXTID.
  3. Click Maintain.
  4. Add the mappings with External ID type set to ID.
  5. Determine Work Area: Entry dialog with External ID set to ID, in Maintain Table Views menu

    The External ID should be the username in Qlik Sense. Usernames in Sense are of the form Domain\User. The User is the SAP username.

    New Entries menu, with External ID specified as Domain name backslash User name, and User specified as SAP username, and Activated check box enabled
  6. Check the Activated box and save the record.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!