Enosix Authentication

generated: '2026-10-20'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.enosix.io/connect/using-the-api/api-key
sources:
- https://docs.enosix.io/connect/using-the-api/api-key
- https://docs.enosix.io/connect/using-the-api/authentication
- https://docs.enosix.io/release/improved-named-credentials
- https://docs.enosix.io/link/configuration/openid-auth
description: Authentication methods for enosix Connect and Link APIs
schemes:
- type: apiKey
  name: API Key
  evidence: Configuring this feature causes the Connect application to authorize all incoming requests have a corresponding X-API-KEY header value
    to the enosix__ApiKey configuration.
  location: header
  header: X-API-KEY
  how_to_obtain: Set a User-Provided Variable with key enosix__ApiKey and a generated opaque token value.
- type: http-basic
  name: Passthrough Basic Authentication
  evidence: In Passthrough mode, you must attach valid SAP credentials to each API request using basic authentication headers.
  location: header
  header: Authorization
  how_to_obtain: Use valid SAP user credentials (username and password) for basic auth.
- type: http-bearer
  name: OpenID Bearer JWT
  evidence: All requests made though API/Proxies that have OpenID Auth configured will require a Bearer JWT (JSON Web Token) authentication header
    provided by the configured OpenID Auth provider.
  location: header
  header: Authorization
  how_to_obtain: Generate a JWT from the configured OpenID provider (e.g., via Postman or Insomnia) and include it in the Authorization header.
note: Configured Connection mode does not require client‑provided credentials; it uses credentials configured on the connection.
docs: https://docs.enosix.io/connect/using-the-api/api-key