website/integrations: Automatic sign-in to HedgeDoc (#4843)

* Automatic sign-in to HedgeDoc

Following the HedgeDoc guides, if you clicks on a HedgeDoc application,
you then still have to click “Sign-in” and “Sign in via authentik” to
actually get signed in.

This patch suggests adding a launch URL to the application which will
cause users to automatically get signed in.

* fix lint

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

---------

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Co-authored-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
Lars Kiesow 2023-03-18 19:29:51 +01:00 committed by GitHub
parent ef028af7d1
commit e35c3d19bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions

View File

@ -19,7 +19,7 @@ The following placeholders will be used:
- `hedgedoc.company` is the FQDN of the HedgeDoc install. - `hedgedoc.company` is the FQDN of the HedgeDoc install.
- `authentik.company` is the FQDN of the authentik install. - `authentik.company` is the FQDN of the authentik install.
Create an application in authentik. Create an OAuth2/OpenID provider with the following parameters: Create an OAuth2/OpenID provider with the following parameters:
- Client Type: `Confidential` - Client Type: `Confidential`
- Scopes: OpenID, Email and Profile - Scopes: OpenID, Email and Profile
@ -27,6 +27,9 @@ Create an application in authentik. Create an OAuth2/OpenID provider with the fo
- Redirect URIs: `https://hedgedoc.company/auth/oauth2/callback` - Redirect URIs: `https://hedgedoc.company/auth/oauth2/callback`
Note the Client ID and Client Secret values. Create an application, using the provider you've created above. Note the Client ID and Client Secret values. Create an application, using the provider you've created above.
To be logged in immediately if you click on the application, set:
- Launch URL: `https://hedgedoc.company/auth/oauth2`
## HedgeDoc ## HedgeDoc