Files
authelia/docs/content/integration/openid-connect/clients/semaphore/index.md
T
2026-09-09 11:35:34 +00:00

3.8 KiB
Raw Blame History

title, description, summary, date, draft, images, weight, toc, aliases, support, seo
title description summary date draft images weight toc aliases support seo
Semaphore Integrating Semaphore with the Authelia OpenID Connect 1.0 Provider. 2025-04-26T11:03:16+00:00 false
620 true
/integration/openid-connect/semaphore/
level versions integration
community true true
title description canonical noindex
Semaphore | OpenID Connect 1.0 | Integration Step-by-step guide to configuring Semaphore with OpenID Connect 1.0 for secure SSO. Enhance your login flow using Authelia’s modern identity management. false

Tested Versions

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

  • Application Root URL: https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/
  • Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
  • Client ID: semaphore
  • Client Secret: insecure_secret

Some of the values presented in this guide can automatically be replaced with documentation variables.

{{< sitevar-preferences >}}

Configuration

Authelia

The following YAML configuration is an example Authelia client configuration for use with Semaphore which will operate with the application example:

identity_providers:
  oidc:
    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    clients:
      - client_id: 'semaphore'
        client_name: 'Semaphore'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: false
        pkce_challenge_method: ''
        redirect_uris:
          - 'https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/api/auth/oidc/authelia/redirect'
        scopes:
          - 'openid'
          - 'profile'
          - 'email'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'

Application

To configure Semaphore there is one method, using the Configuration File.

Configuration File

{
  "oidc_providers":  {
    "authelia": {
      "display_name": "Authelia",
      "provider_url": "https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}",
      "client_id": "semaphore",
      "client_secret": "insecure_secret",
      "redirect_url": "https://semaphore.{{< sitevar name="domain" nojs="example.com" >}}/api/auth/oidc/authelia/redirect",
      "scopes": ["openid", "profile", "email"],
      "username_claim": "preferred_username",
      "email_claim": "email",
      "name_claim": "name",
      "order": 1
    }
  }
}

See Also