Zylon · Authentication Profile

Zylon Authentication

Authentication

Zylon secures its APIs with http, oauth2, and openIdConnect across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

Company
Methods: http, oauth2, openIdConnect Schemes: 3 OAuth flows: authorizationCode API key in: header

Security Schemes

BearerToken http
scheme: bearer
CredentialsSession http
scheme: session
OpenIDConnect openIdConnect

Source

Authentication Profile

zylon-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://docs.zylon.ai/en/developer-manual/build-with-zylon/workspace-api/authentication/auth
docs: https://docs.zylon.ai/en/developer-manual/build-with-zylon/workspace-api/authentication/openid
summary:
  types: [http, oauth2, openIdConnect]
  api_key_in: [header]
  oauth2_flows: [authorizationCode]
  note: >-
    Zylon is deployed on-premise; there is no single hosted base URL. All calls
    target the customer's own deployment host ({BASE_URL}). Auth is documented,
    not derived from a published OpenAPI (none is published publicly).
schemes:
- name: BearerToken
  type: http
  scheme: bearer
  description: >-
    API token passed as `Authorization: Bearer {API_TOKEN}` on every ZylonGPT
    and Workspace API request.
  source: docs
- name: CredentialsSession
  type: http
  scheme: session
  description: >-
    POST /api/v1/auth/login exchanges email + password for an account session;
    POST /api/v1/auth/register creates a credentials account. When LDAP is
    enabled the server attempts LDAP first then falls back to local credentials.
  source: docs
- name: OpenIDConnect
  type: openIdConnect
  description: >-
    SSO login redirects (Google / Microsoft) and integration OAuth flows for
    Confluence and SharePoint via the Workspace API OpenID & OAuth endpoints.
  source: docs
directory_integration:
- Active Directory / LDAP (enterprise directory integration, added v1.56.0)