Prerequisites
-
Configure at least one virtual appliance cluster and successfully test the connection. For instructions, refer to the Virtual Appliance Reference Guide.
-
Verify that an MS SQL Server database is installed in your environment. For more information, refer to MS SQL Database Setup Considerations.
-
Ensure to perform the data extraction process to import the latest Imprivata EAM data into the MS SQL database. For more information, refer to Aggregation Considerations.
-
Verify Provisioning System Adaptor Name is configured in your Imprivata source. If it does not already exist, you must manually create it. For more information, refer to Provisioning System Adaptor Settings Requirements. To provide necessary API access permissions to Provisioning System Adaptor, refer to API Access Settings Requirements.
MS SQL Database Setup Considerations
If you are installing the MS SQL database setup for the first time, follow these steps:
-
Verify that an MS SQL Server database can be accessed by both the Imprivata EAM and SailPoint Virtual Appliance (VA).
-
Use the provided MS SQL script to create the required database and table.
The script sets up the Imprivata database and creates a minimum-permission user with the username Imprivata, which is used for source configuration. You can modify the database name, user permissions, and username / password before running the script.
Aggregation Considerations
-
Aggregation relies on the MS SQL database. You must perform the data extraction process to import the latest Imprivata EAM data into the MS SQL database. To keep the MS SQL database updated, periodically run data extraction to enable the connector to aggregate the latest data. For more information, refer to Updating MS-SQL Database Configuration for Data Extraction .
-
After creating a user, it will not be immediately included in the MS SQL database. Run the data extraction process before performing any further operations on the user.
-
During account aggregation, only Proximity Device IDs are fetched from Imprivata EAM managed system. All other details are sourced from the MS SQL database.
-
Account aggregation and entitlement aggregation utilize data from the MS SQL database. To keep MS SQL data in sync with real-time data, regularly run the data extraction process.
Provisioning System Adaptor Settings Requirements
Follow the steps below to identify and activate a Provisioning System Adaptor:
-
Find the Provisioning System Adaptor Name in your Imprivata source.
To find the Provisioning System Adaptor Name in your Imprivata administrative console:
-
Select the gear box in the top right corner of the Imprivata Enterprise Access Management interface to access the settings.
-
Select SPML Provisioning.
The List of Provisioning System Adaptors will be displayed. If none exist, create a new Provisioning System Adaptor.
-
Enable the desired adaptor before use.
-
On the SPML provisioning page, select the Yes radio button for the "Enable Client Request Authentication?" option.
-
Select Save to save the settings.
-
-
Go to Imprivata EAM integration Connection Settings page to complete further configuring steps with the managed system. For more information, refer to Connection Settings.
API Access Settings Requirements
Follow the steps below to ensure that the Provisioning System Adaptor has the necessary API access permissions to function correctly within your Imprivata Enterprise Access Management environment:
-
Select the gear icon in the top-right corner of the Imprivata Enterprise Access Management interface to access the settings.
-
Select API Access.
-
In the API Access, select the option Allow full API Access via ProveID Web and ProveID Embedded to enable API access for the Provisioning System Adaptor.
-
Choose the appropriate API access setting based on your Imprivata Enterprise Access Management version:
-
For version 25.2 and later, select Sailpoint.
-
For version 25.1 and earlier, select Future 7.
-
Certificate Requirements
You can set up any SSL or TLS certificate required for configuring Imprivata EAM integration with the MS SQL Server by following the instructions provided in the Uploading a Certificate Manually to a Virtual Appliance.