Alerta Authentication

generated: '2026-10-26'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.alerta.io/webui/apikeys.html
sources:
- https://docs.alerta.io/webui/apikeys.html
- https://docs.alerta.io/authentication.html
- https://docs.alerta.io/gettingstarted/tutorial-6-auth.html
- https://docs.alerta.io/webui/authentication.html
description: Authentication methods documented for Alerta
schemes:
- type: http-basic
  name: Basic Auth
  evidence: The most straight-forward authentication strategy to implement of the four is HTTP Basic Authentication provided by the Alerta API
    because there is no additional configuration required of the Alerta server to use it other than setting AUTH_REQUIRED to True .
  location: header
  header: Authorization
  how_to_obtain: Users sign up via the web UI or using the CLI and then login to receive a JWT token.
- type: apiKey
  name: API Keys
  evidence: The API Keys page allows you to create and manage API keys used to authenticate with the Alerta API.
  how_to_obtain: Create a new API key via the Alerta UI (Configuration > API Keys) or through the API.
- type: oauth2
  name: GitHub OAuth2
  evidence: To use GitHub as the OAuth2 provider for Alerta, login to GitHub and go to Settings -> Applications -> Register New Application .
  how_to_obtain: Register an application in GitHub and configure Alerta to use it.
- type: other
  name: HMAC Auth
  evidence: 'Alerta also supports two “machine-to-machine” authentication strategies: API Keys, HMAC Auth'
docs: https://docs.alerta.io/webui/apikeys.html