2.4 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
BookStack | Integrating BookStack with the Authelia OpenID Connect Provider. | 2022-06-15T17:51:47+10:00 | false |
|
620 | true | true |
Tested Versions
Before You Begin
You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it's completely up to you.
This example makes the following assumptions:
- Application Root URL:
https://bookstack.example.com
- Authelia Root URL:
https://auth.example.com
- Client ID:
bookstack
- Client Secret:
bookstack_client_secret
Important Note: Bookstack does not properly URL encode the secret per RFC6749 Appendix B at the time this article was last updated (noted at the bottom). This means you'll either have to use only alphanumeric characters for the secret or URL encode the secret yourself.
Configuration
Application
To configure BookStack to utilize Authelia as an OpenID Connect Provider:
- Edit your .env file
- Set the following values:
- AUTH_METHOD:
oidc
- OIDC_NAME:
Authelia
- OIDC_DISPLAY_NAME_CLAIMS:
name
- OIDC_CLIENT_ID:
bookstack
- OIDC_CLIENT_SECRET:
bookstack_client_secret
- OIDC_ISSUER:
https://auth.example.com
- OIDC_ISSUER_DISCOVER:
true
- AUTH_METHOD:
Authelia
The following YAML configuration is an example Authelia client configuration for use with BookStack which will operate with the above example:
- id: bookstack
description: BookStack
secret: bookstack_client_secret
public: false
authorization_policy: two_factor
redirect_uris:
- https://bookstack.example.com/oidc/callback
scopes:
- openid
- profile
- email
userinfo_signing_algorithm: none