Virtru Authentication
The Virtru Data Security Platform (OpenTDF) authenticates all service calls with OpenID Connect (OIDC) / OAuth 2.0. Clients obtain an access token from the platform's configured identity provider (Keycloak by default) and present it as a Bearer token on every Connect/gRPC request to the Policy, Key Access (KAS), Authorization, Entity Resolution and Well-Known services. Key operations additionally use PKCS#11 for HSM-backed key material and ABAC (attribute-based access control) for authorization decisions.
Virtru secures its APIs with oauth2 and openIdConnect across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials and authorizationCode flow(s).
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.