Tintri · Authentication Profile

Tintri Authentication

Authentication

The Tintri VMstore REST API (v310) uses session-based authentication. A client authenticates with local or directory-service credentials by POSTing to the session/login endpoint; the server returns a session cookie (JSESSIONID) that must accompany subsequent requests. There is no OAuth 2.0 / OpenID Connect flow and no long-lived API-key surface — sessions are short-lived and are explicitly closed via session/logout. Because there is no OAuth scope model, no scopes/ artifact is produced; role-based access control is enforced by the appliance against the authenticated user's assigned UserRole.

Tintri secures its APIs with session across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyStorageData ManagementInfrastructureVirtualizationCloudKubernetesDevOpsEnterpriseREST API
Methods: session Schemes: 1 OAuth flows: API key in:

Security Schemes

sessionAuth session
scheme: cookie

Source

Authentication Profile

tintri-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://tintri.github.io/tintri-rest-api/index.html
docs: https://tintri.github.io/tintri-rest-api/index.html
description: >-
  The Tintri VMstore REST API (v310) uses session-based authentication. A client
  authenticates with local or directory-service credentials by POSTing to the
  session/login endpoint; the server returns a session cookie (JSESSIONID) that
  must accompany subsequent requests. There is no OAuth 2.0 / OpenID Connect
  flow and no long-lived API-key surface — sessions are short-lived and are
  explicitly closed via session/logout. Because there is no OAuth scope model,
  no scopes/ artifact is produced; role-based access control is enforced by the
  appliance against the authenticated user's assigned UserRole.
summary:
  types: [session]
  api_key_in: []
  oauth2_flows: []
schemes:
- name: sessionAuth
  type: session
  scheme: cookie
  cookie_name: JSESSIONID
  login: POST /api/v310/session/login
  login_body: '{ "username": "...", "password": "...", "typeId": "com.tintri.api.rest.vcommon.dto.rbac.RestApiCredentials" }'
  logout: GET /api/v310/session/logout
  authorization_model: role-based access control (UserRole) enforced by the appliance
  sources: [docs]