Alkira · Authentication Profile

Alkira Authentication

Authentication

Alkira secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyEnterpriseNetworkingCloudMulti-CloudInfrastructureNetwork as a ServiceSD-WANSecurityAutomation
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header ()
legacy-basic http
scheme: basic

Source

Authentication Profile

alkira-authentication.yml Raw ↑ 
generated: '2026-07-17'
method: searched
source: https://registry.terraform.io/providers/alkiranet/alkira/latest/docs
# Derived from Alkira's official Terraform provider docs and the client-go client
# implementation (github.com/alkiranet/client-go, vendored in alkiranet/mcp-alkira).
docs: https://registry.terraform.io/providers/alkiranet/alkira/latest/docs
summary:
  types: [apiKey]
  api_key_in: [header]
  header: Authorization
  scheme_note: 'API key is base64-encoded and prefixed: Authorization: api-key <base64(api_key)>'
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter_name: Authorization
  format: 'api-key <base64(API_KEY)>'
  provisioning: Portal > Settings > User Management (per-user key)
  env_vars: [ALKIRA_PORTAL, ALKIRA_API_KEY]
  primary: true
- name: legacy-basic
  type: http
  scheme: basic
  deprecated: true
  deprecation_note: 'Username/password authentication (ALKIRA_USERNAME / ALKIRA_PASSWORD)
    is deprecated and will be removed in a future major release; migrate to API key auth.'
notes:
- Auth is tenant-scoped by the portal host (<tenant>.portal.alkira.com); the client
  resolves the tenant network id via GET /api/tenantnetworksummaries after auth.
- No OAuth2/OIDC surface is documented; there is no scope model (skip scopes/).