Connecting SailPoint and SAP HANA

To connect SailPoint with SAP HANA, perform the following tasks:

Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

To configure a new source:

1. Sign in to SailPoint.
2. Go to Admin > Connections > Sources.
3. Select Create New.
4. Search for the connector by entering the name in the search box, and then select Configure.
5. In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
6. In the Description field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
7. In the Source Owner field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to Assigning a Source Owner.

8. Under Connection Type, select Direct Connection or Flat File.

   • Direct Connection - A direct connection fetches data from the Virtual Appliance Cluster you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the Virtual Appliance Reference Guide.
   • Flat File - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable.

9. If you selected Direct Connection, in Virtual Appliance Cluster, select the virtual appliance cluster that will be used as the application connector for the source.

10. (Optional) Select a governance group to grant its members source or role sub-admin level oversight of the source and its access. For more information, refer to Creating and Managing Governance Groups.
11. If this source represents a primary system containing your organization's personnel records, select the Authoritative Source checkbox. For more information, refer to Creating Identity Profiles.
12. Select Continue. The source is created, and you are navigated to the Source Setup > Base Configuration page. Continue to configure your connected source there.

Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.

2. In the Source Owner dropdown list, select the identity that owns this source.

   • To find a source owner, begin entering their name.

3. In the Virtual Appliance Cluster dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to SailPoint Virtual Appliances.

4. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

   Note

   To add a credential provider, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

5. Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.

6. (Optional) In the Governance Group for Source Management dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to Associating Governance Groups with a Source.

7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   • Enable Provisioning - Set the toggle to Enabled to allow the source to create, update, and deactivate accounts in the connected source system.

   • Disable Provisioning - Set the toggle to Disabled to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.

8. Select Save.

Connector Files

1. Upload the .jar file used for the source. The .jar file in this case is the ngdbc.jar file located in the <sap_client_install_dir>\hdbclient directory, where <sap_client_install_dir> is the SAP Client Installation directory.

   Warning

   Ensure that the file you upload is not vulnerable or malicious.

2. Select Save.

Connection Settings

1. Enter the Username of the SAP HANA service account that is used for the source.
2. Enter the Password associated to the user.

3. Enter the SAP HANA Database URL.

   • Default Database: jdbc:sap://<HOST>:<PORT>/?databaseName=<dbName>

   • SAP HANA Cloud Database: jdbc:sap://SQL-ENDPOINT/?encrypt=true

     For more information, refer to the SAP Help Portal.

   Where:

   • <HOST>: is the server name where the SAP HANA database is installed.
   • <PORT>: is the port on which the database is configured.
   • <dbName>: is the name of the database to connect to.
   • SQL-ENDPOINT: is the SQL Endpoint contain the SAP HANA Cloud database instance ID and port.

   The specified default URL is provided for the multi-tenant HANA Database system. For a single tenant HANA Database system, the attribute database name is not applicable.

4. Enter the Driver Class of the jar file used for the source.

5. Select Save.

Additional Configuration

1. Enter the Page Size, which is the number of records that you want to aggregate in a single page.

2. SAP HANA supports aggregation of future dated accounts. Use the Aggregate Future Dated Accounts option to change the behavior for Enable and Disable operations. After adding the manageFutureDatedAccounts attribute:

   • Disabling the account deactivates the user and sets the user's end date to the current date.
   • Enabling the account activates the user and sets the user's start date to the current date.

   SAP HANA supports the following attributes for updating an account:

   • IS_CLIENT_CONNECT_ENABLED
   • EMAIL_ADDRESS
   • TIME_ZONE
   • VALID_FROM
   • VALID_UNTIL
   • DISABLE_PASSWORD
   • IS_RESTRICTED

3. Use the Aggregate Terminated Accounts toggle if you want to aggregate inactive users whose valid end date is in past. Specify the Effective Date in the MM/DD/YYYY format from when you want to aggregate the terminated accounts. The date must not be in the future. The Effective Date is only applicable if you enable the Aggregate Terminated Accounts option. The value of the Effective Date is mapped to the 'Valid_Until' date for the inactive users. Using the Aggregate Terminated Accounts option changes the behavior for the Enable and Disable feature:

   • Disabling the account operation deactivates the user and sets the user's end date to the current date.
   • Enabling the account operation activates the user and sets the user's start date to the current date.

4. Select Save.

Provisioning Settings

Configure settings related to provisioning operations.

Revoke Catalog Roles

By default, users can only revoke catalog roles that they grant to other users. You can allow users to revoke catalog roles that were granted by other users. To revoke roles granted by others, the service account must either have the ROLE ADMIN system privilege or be assigned the same catalog role with the ADMIN OPTION.

To enable users to revoke catalog roles granted by other users:

1. Enable Revoke Catalog Roles Granted by Others.
2. Select Save.

SSL Connection

The SAP HANA source supports SSL connections.

Perform the following steps to enable the SSL connection to the SAP HANA database:

1. Import the SSL certificates from the SAP HANA Server to the /home/sailpoint/certificates directory on the source VA.

2. In the hosts.yaml file enter the SAP HANA Server in the xxx.xx.xx.xxx <sap hana server hostname> format.

   Note

   For information on creating a hosts.yaml file, refer to Configuring a Hosts.yaml File.

3. Restart the CCG with the sudo systemctl restart ccg command.

4. In the configuration of the SAP HANA source for the Database URL field, use the following URL mentioned in the SSL certificate:

   jdbc:sap://:/?databaseName=&encrypt=true&hostNameInCertificate=<HostName mentioned in certificate>

Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to Review and Test.

2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.

3. Select Test Connection.

SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to Discovered Applications in the SailPoint user interface.

For more information, refer to Application Onboarding in the SailPoint SaaS documentation.

Additional Authentication Resources

For more information on utilizing authentication with your SAP HANA Database connector, refer to the following links on the SAP Help Portal:

• For information on Kerberos and SAML 2.0 authentication, refer to SAP HANA Authentication and Single Sign-On.

  Note

  The SailPoint SAP HANA connector currently supports password authentication only. If required, password creation can be disabled, which allows creation of a user without a password. The connector has been enhanced to provide support for Kerberos and SAML (Security Assertion Markup Language) authentication mechanisms along with password authentication. Users can be created by choosing any of the authentication options or all of the options together.

• For more information on supported user authentication methods, refer to Supported Authentication Methods.

• For more information on using single sign-on (SSO) using Kerberos, refer to Single Sign-On Using Kerberos.
• For information on how Kerberos constrained delegation works, refer to Introduction to Kerberos Constrained Delegation - SAP HANA Smart Data Access HANA to HANA Scenarios.
• For more information on using SSO using SAML 2.0, refer to Single Sign-On Using SAML 2.0.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.