Skip to main content

Integrate with Semaphore UI

Support level: Community

What is Semaphore UI?​

Semaphore UI is a modern web interface for managing popular DevOps tools.

-- https://semaphoreui.com/

Preparation​

The following placeholders are used in this guide:

  • semaphore.company is the FQDN of the Semaphore installation.
  • authentik.company is the FQDN of the authentik installation.
info

This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.

authentik configuration​

Redirect URI changes in authentik 2026.5

In authentik versions earlier than 2026.5, all Redirect URIs are automatically treated as Authorization type. If you are using one of these older authentik versions, add only the Authorization URL to your Redirect URIs and do not configure a Post Logout URI.

To support the integration of Semaphore UI with authentik, you need to create an application/provider pair in authentik.

Create an application and provider​

  1. Log in to authentik as an administrator and open the authentik Admin interface.

  2. Navigate to Applications > Applications and click New Application to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.)

    • Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the Slug value because it will be required later.
    • Choose a Provider type: select OAuth2/OpenID Connect as the provider type.
    • Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
      • Note the Client ID and Client Secret values because they will be required later.
      • Add a Redirect URI of type Strict Authorization as https://semaphore.company/api/auth/oidc/authentik/redirect/.
      • Select any available signing key.
    • Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.

  3. Click Submit to save the new application and provider.

Semaphore UI configuration​

Log in to your Semaphore UI host via SSH. Edit the /etc/semaphore/config.json file with the text editor of your choice.

Add the oidc_providers configuration:

/etc/semaphore/config.json
{
    "oidc_providers": {
        "authentik": {
            "display_name": "Sign in with authentik",
            "provider_url": "https://authentik.company/application/o/<application_slug>/",
            "client_id": "<Client ID from authentik>",
            "client_secret": "<Client Secret from authentik>",
            "redirect_url": "https://semaphore.company/api/auth/oidc/authentik/redirect/",
            "username_claim": "preferred_username",
            "name_claim": "preferred_username",
            "email_claim": "email",
            "scopes": ["openid", "profile", "email"]
        }
    }
}
Provider name

The oidc_providers key, such as authentik, must match the provider name in the redirect URL.

Web root

If a Not Found error is displayed after login, you might need to set web_root to / (see semaphoreui/semaphore#2681):

.env
SEMAPHORE_WEB_ROOT=/

Users are created when they log in with authentik. They do not have permissions to create resources initially. These permissions must be assigned by the local administrator that was created during the first Semaphore UI login.

Configuration verification​

To confirm that authentik is properly configured with Semaphore UI, log out, open Semaphore UI, and click the SSO login button. You should be redirected to authentik and then back to Semaphore UI.

Resources​