Enterprise Vault™ Compliance Accelerator Administrator's Guide
- Introducing Compliance Accelerator
- Product documentation
- Introducing the Compliance Accelerator client
- Setting up employees and employee groups
- Working with departments
- Implementing Chinese Walls security
- Managing exception employees
- Grouping departments into partitions
- Using attributes to classify departments
- Searching for items
- About searching with Compliance Accelerator
- Building Compliance Accelerator search schedules
- Using hotwords to search for items
- Manually reviewing items
- About reviewing with Compliance Accelerator
- Escalating items
- Working with research folders
- Exporting items
- Creating and viewing reports
- Available Compliance Accelerator reports
- About viewing Compliance Accelerator datasets using the OData web service
- Appendix A. Customizing Compliance Accelerator
- Setting Compliance Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Troubleshooting
- Issues with Compliance Accelerator reports
Error messages when the Intelligent Review (IR) API authentication and authorization fails
This is a Kerberos double hop error. This error appears if the Kerberos constrained trusted delegation is not set correctly between the Compliance Accelerator Server and the Compliance Accelerator Database Server.
To fix this error, perform the following steps:
Verify if the Compliance Accelerator Server is trusted for delegation.
Check if the installation setup/environment has Kerberos constrained trusted delegation is set properly. Verify the SQL Service Service Principal Names (SPNs) for correctness, duplication, and missing SPNs. Use the Kerberos Configuration Manager tool.
Verify if the Compliance Accelerator Server is using Fully Qualified Domain Name (FQDN) and not IP Addresses for connecting to the Compliance Accelerator Configuration and the customer databases. For configuration database, verify if the <install dir \Veritas Intelligent Review\IR.APIEndPoint \appsettings.json-> ConfigDBConnection key is using the FQDN and not IPAddress for connection string. For the customer database, verify if the configuration database->tblCustomer table for the 'Server' field for that customer is using FQDN and not IPAddress.
Verify if the SQL Server service account is a user, then that user is trusted for delegation, and various properties like the user is allowed for the delegation are set correctly.
Refer to the sample screen below.
To fix this issue, perform the following procedure:
- Create the correct SPNs. For example, If the SQL Service is running as a Vault Service account (VSA) user, create or check if proper SPNs exist for VSA.
- Create SPNs for the availability group listener as well as the actual SQL nodes.
- Enable the Compliance Accelerator Server to trust for delegation (only the listener). Refer to the sample image below.
Note:
Choose Add… while trusting for delegation and choose the SQL Service account (VSA) on which the SPNs are configured.
- Restart the Active Directory Domain service on the Domain Controller.
- Restart Internet Information Services (IIS) on the Compliance Accelerator Server.
- Call the Intelligent Review (IR) API directly or via Enterprise Vault. Refer to the sample image below.