habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website/integrations: Update to Wizard and Styling Guide (#12919)

Browse Source 
* update to Wizard and Styling Guide

* Ready for PR

* remove changes on actual budget 

https://github.com/goauthentik/authentik/pull/12716

Signed-off-by: NiceDevil <17103076+nicedevil007@users.noreply.github.com>

---------

Signed-off-by: NiceDevil <17103076+nicedevil007@users.noreply.github.com>
Co-authored-by: nicedevil007 <nicedevil007@users.noreply.github.com>
This commit is contained in:
NiceDevil
2025-02-17 21:33:07 +01:00
committed by GitHub
parent e7538b85e1
commit 179f5c7acf
4 changed files with 116 additions and 138 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
website/integrations/services/semaphore/index.mdx
View File

@ -28,27 +28,14 @@ This documentation lists only the settings that you need to change from their de
## authentik configuration
Start the wizard for adding a new application.
[Create](https://docs.goauthentik.io/docs/add-secure-apps/applications/manage_apps#add-new-applications) an OAuth2/OpenID provider and an application in authentik. Use the following parameters for the OAuth2/OpenID provider:
**1. Application:**
- Name: `Semaphore UI`
- Slug: `semaphore`
**2. Choose a Provider**
Select `OAuth2/OpenID Provider`
**3. Configure Provider**
Select implicit or explicit authorization flow as desired.
Take note of the Client ID and Client Secret, you'll need to give them to Semaphore UI later.
- Redirect URIs/Origins (RegEx): `https://semaphore.company/api/auth/oidc/authentik/redirect/`
- Signing Key: `authentik Self-signed Certificate`
Leave the rest as default values.
1. In the authentik Admin interface, navigate to **Applications** -> **Applications**.
2. Use the wizard to create a new application and provider. During this process:
- Note the **Client ID**, **Client Secret**, and **slug** values for later use.
- Select implicit or explicit authorization flow as desired.
- Set the redirect URI to <kbd>https://<em>semaphore.company</em>/api/auth/oidc/authentik/redirect/</kbd>.
- Select any available signing key.
## Semaphore UI configuration
@ -60,7 +47,7 @@ Add the `oidc_providers` configuration:
{
"oidc_providers": {
"authentik": {
"display_name": "Sign in with Authentik",
"display_name": "Sign in with authentik",
"provider_url": "https://authentik.company/application/o/<slug>/",
"client_id": "<client-id>",
"client_secret": "<client-secret>",
@ -89,14 +76,12 @@ SEMAPHORE_WEB_ROOT: /
More information on this can be found in the Semaphore documentation https://docs.semaphoreui.com/administration-guide/openid/authentik/.
Leave the rest as default.
## Test the login
- Open a browser of your choice and open the URL `https://semaphore.company`.
- Open a browser of your choice and open the URL <kbd>https://<em>semaphore.company</em></kbd>.
- 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.
- You should be redirected to authentik (with the login flows you created) and then authentik should redirect you back to <kbd>https://<em>semaphore.company</em></kbd> URL.
- If you are redirected back to the <kbd>https://<em>semaphore.company</em></kbd> 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 admin created during the first login to the Semaphore UI.