Veritas™ Surveillance User Guide
- Introducing Veritas Surveillance
- Getting started
- Working with dashboard widgets
- Managing employees and employee groups
- Managing departments
- Managing department users
- Managing department-level archives
- Managing department-level searches
- Managing department-specific hotword sets
- Managing department-specific labels
- Managing department-specific review comments
- Viewing employees associated with departments
- Managing users, roles, and permissions
- Managing application-level archives
- Managing application-level searches
- Managing application-specific hotword sets
- Managing application-specific labels
- Managing application-specific review comments
- Managing search schedules
- Managing export operations
- Managing reviews
- Working with reports
- Enhanced reporting
- Departments API
- Roles API
- Users API
- UserRoles API
- ItemMetrics API
- ReviewerMapping API
- MonitoredEmployees API
- Evidence of Review API
- Managing Power BI templates for reporting APIs
- Managing Audit Settings
- Working with Audit viewer
Authentication
To ensure the security and integrity of data access, the Reporting API requires authentication. Authentication is used to verify the identity of the requesting client or application and determine whether it has the necessary permissions to access the API resources. There are two primary authentication methods supported for this API:
Upon configuring the reporting endpoint API, a Base URL, a primary and secondary API Keys are generated. Include either primary or secondary API key in the
header of your API requests.For example,
X-API-Key:<Primary or Secondary API Key>
Basic Authentication is a method where API clients provide a username and password with each request. Users use an encoded string in the Authorization header for this method. The recipient of the request uses this string to verify the users' identity and their access rights to a resource.
For example,
Authorization: Basic <Base64 encoded credentials>
To generate a Base64 encoded credentials:
Combine the credentials (username and password) with a colon (:).
Note:
The username must be
. The password can be either a primary or a secondary API Key provided after configuring the reporting endpoint. Use either one as your password.For example, ReportingApiUser:32adasdf3asdcvzxcweasd
After specifying the credentials as mentioned in the step above, generate a Base64 encoded credentials. It is required while setting authorization header.
For example, dGVuYW50OmtleQ==
Therefore, requests made by this user would be sent with the following header:
Authorization: Basic dGVuYW50OmtleQ==
When a server receives this request, it can access the Authorization header, decode the credentials, and look up the user to determine whether access to the requested resource should be allowed.