Versori Authentication

generated: '2026-10-21'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.versori.com/latest/how-it-works/connect.md
sources:
- https://docs.versori.com/latest/how-it-works/connect.md
- https://docs.versori.com/latest/guides/getting-started/connect/bypass-auth.md
- https://docs.versori.com/latest/guides/auth-methods/introduction.md
- https://docs.versori.com/latest/guides/auth-methods/api-key.md
description: Authentication methods supported by Versori as documented.
schemes:
- type: oauth2
  name: OAuth 2.0
  evidence: OAuth 2.0 is a standard authentication method for web applications, and is the one most recommended to use where the system being
    integrated supports it.
  flows:
  - authorization_code
  - client_credentials
  - password
  - refresh_token
- type: apiKey
  name: API Key
  evidence: API Key is a standard authentication method for API applications. Versori supports arbitrary API keys which can be set in the header,
    query string or cookie.
- type: http-bearer
  name: Bearer
  evidence: 'HTTP Authorization is a standard authentication method for HTTP applications where the credential is set in the "Authorization" header.
    Versori supports the following authorization schemes: * Bearer'
  location: header
  header: Authorization
- type: other
  name: No Auth
  evidence: This creates an authentication method called "No Auth" with the type set to "None - Authentication Bypassed".
docs: https://docs.versori.com/latest/how-it-works/connect.md
note: 1 extracted row(s) were dropped because their quote was not on the page.