6d4c9a3446
* Typo and improved language * Changes "admin" to "administrator" and updates indentation * Updates miniflux to newer styling * Combines two notes at beginning of jellyfin doc into one * Replaces all "your application slug" with "application_slug" and replaces tags that are no longer in use * Replaces tags that are no longer in use * Updates immich indentation, application_slug and removes tags * Updated bookstack indentation, tags and application slug * Removes kbd and em tags, and updates the application slug * Gix metadata header in bookstack doc * Lint fix miniflux * ArgoCD indentation --------- Signed-off-by: Dewi Roberts <dewi@goauthentik.io>
95 lines
3.9 KiB
Plaintext
95 lines
3.9 KiB
Plaintext
---
|
|
title: Integrate with Semaphore UI
|
|
sidebar_label: Semaphore
|
|
support_level: community
|
|
---
|
|
|
|
## What is Semaphore UI
|
|
|
|
> Semaphore UI is a modern web interface for managing popular DevOps tools.
|
|
>
|
|
> -- https://semaphoreui.com/
|
|
>
|
|
> This guide explains how to configure Semaphore UI to use authentik as the OAuth provider for logging in to the Web GUI.
|
|
|
|
## 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.
|
|
|
|
:::note
|
|
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
|
|
|
|
To support the integration of Semaphore with authentik, you need to create an application/provider pair in authentik.
|
|
|
|
### Create an application and provider in authentik
|
|
|
|
1. Log in to authentik as an administrator and open the authentik Admin interface.
|
|
2. Navigate to **Applications** > **Applications** and click **Create with Provider** 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.
|
|
- **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**,**Client Secret**, and **slug** values because they will be required later.
|
|
- Set a `Strict` redirect URI to `https://semaphore.company/api/auth/oidc/authentik/redirect`.
|
|
- Select any available signing key.
|
|
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** 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:
|
|
|
|
```
|
|
{
|
|
"oidc_providers": {
|
|
"authentik": {
|
|
"display_name": "Sign in with authentik",
|
|
"provider_url": "https://authentik.company/application/o/<slug>/",
|
|
"client_id": "<client-id>",
|
|
"client_secret": "<client-secret>",
|
|
"redirect_url": "https://semaphore.company/api/auth/oidc/authentik/redirect/",
|
|
"username_claim": "username",
|
|
"name_claim": "name",
|
|
"email_claim": "email",
|
|
"scopes": ["openid", "profile", "email"]
|
|
}
|
|
},
|
|
...
|
|
}
|
|
```
|
|
|
|
:::info
|
|
The name of the oidc_provider (e.g. `authentik`) needs to match the name on the redirect URL.
|
|
:::
|
|
|
|
:::info
|
|
If a `Not Found` error is displayed after the login, you might need to set the web_root to `/` (see https://github.com/semaphoreui/semaphore/issues/2681):
|
|
|
|
```
|
|
SEMAPHORE_WEB_ROOT: /
|
|
```
|
|
|
|
:::
|
|
|
|
More information on this can be found in the Semaphore documentation https://docs.semaphoreui.com/administration-guide/openid/authentik/.
|
|
|
|
## Test the login
|
|
|
|
- Open a browser of your choice and open the URL `https://semaphore.company`.
|
|
- Click on the SSO-Login button.
|
|
- You should be redirected to authentik (with the login flows you created) and then authentik should redirect you back to `https://semaphore.company` URL.
|
|
- If you are redirected back to the `https://semaphore.company` URL you did everything correct.
|
|
|
|
:::info
|
|
Users are created upon logging in with authentik. They will not have the rights to create anything initially. These permissions must be assigned later by the local administrator created during the first login to the Semaphore UI.
|
|
:::
|