Armada · Authentication Profile

Armada Authentication

Authentication

Armada secures its APIs with http and openIdConnect across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyEdge ComputingGPU CloudInfrastructureArtificial IntelligenceKubernetesBare MetalIoTOrchestrationSovereign Cloud
Methods: http, openIdConnect Schemes: 3 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
modelServiceApiKey http
scheme: bearer
consoleOIDC openIdConnect

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/armada-orchestrator-openapi-original.yml
docs: https://docs.armada.ai/bridge/tenant-guide/ai-studio/model-as-a-service/api-key
summary:
  types:
  - http
  - openIdConnect
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: >-
    Orchestrator API: JWT Bearer token in the Authorization header, issued by the
    platform auth middleware.
  sources:
  - openapi/armada-orchestrator-openapi-original.yml
- name: modelServiceApiKey
  type: http
  scheme: bearer
  description: >-
    Bridge AI Studio Model-as-a-Service: an API key presented as a Bearer token
    (Authorization: Bearer $API_KEY). Keys are created and revoked in AI Studio
    Settings and shown once at creation.
  sources:
  - https://docs.armada.ai/bridge/tenant-guide/ai-studio/model-as-a-service/api-key
- name: consoleOIDC
  type: openIdConnect
  description: >-
    Console/UI sign-in (console.armada.ai, Atlas / Armada Edge Platform) is OIDC,
    backed by Keycloak.
  sources:
  - https://console.armada.ai/