trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website/integrations: fix Vikunja setup instructions (#4730) 

* fix: Vikunja setup instructions

Signed-off-by: kolaente <k@knt.li>

* fix: clarify what needs restarting after config change

---------

Signed-off-by: kolaente <k@knt.li>
This commit is contained in:
kolaente 2023-02-22 16:31:18 +01:00 committed by GitHub
parent cd99b6e48f
commit 60d3da20f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
website/integrations/services/vikunja/index.md
View File

@ -37,6 +37,7 @@ Only settings that have been modified from default have been listed.
- Name: Vikunja
- Client ID: Copy and Save this for Later
- Client Secret: Copy and Save this for later
- Signing Key: Select one of the available signing keys (Without this, Vikunja will not recognize Authentik's signing key method as a valid one and the login will not work)
- Redirect URIs/Origins:
```
@ -82,7 +83,11 @@ auth:
```
:::note
Vikunja Reference link: https://vikunja.io/docs/config-options/#auth
You need to restart the Vikunja API after applying the OpenID configuration to Vikunja.
:::
:::note
Vikunja Configuration Reference: https://vikunja.io/docs/config-options/#auth
:::
### Step 3
@ -93,9 +98,3 @@ In authentik, create an application which uses this provider. Optionally apply a
- Slug: vikunja
- Provider: vikunja
- Launch URL: https://vik.company
## Notes
:::note
It is recommended to restart all Vikunja components (API and frontend) after applying the OpenID configuration to Vikunja.
:::