BookStack
BookStack
This integration guide is community supported. It's not guaranteed to be complete, accurate, or up-to-date. It's likely that if this integration guide does not work for you that changes occurred with a third-party application.
Important Note: This documentation is version specific. Make sure you check the section outlining the tested versions.
Important Note: We always recommend users read the third-party documentation as part of the integration process to ensure configuration elements matches their needs. As such the See Also section is likely to have important links.
Important Note: If you find an error in this documentation please make a Pull Request, start a Discussion, or contact us on a Chat Room.
Tested Versions
Before You Begin
Important Reading
This section contains important elements that you should carefully consider before configuration of an OpenID Connect 1.0 Registered Client.
Known Bugs
Client Has Known Significant Bugs
Unfortunately at the time this guide was last modified (noted at the bottom of the guide) this third-party application has bugs which are significant and indicate either a fairly low level of support for OpenID Connect 1.0 or no effective support at all. This guide may have workarounds to adapt to this but this is done solely on a best effort basis. The developers of the application should be encouraged to fix these bugs.
Client Credentials Encoding: this client does not properly encode the client credentials before
using them for authentication as per
RFC6749 Appendix B. It is
required that the Client ID and Client Secret are both URL Escaped before being used for both the
client_secret_post
and client_secret_basic
authentication mechanisms. Avoiding special
characters in both the Client ID and Client Secret or URL Escaping them before adding them to the clients
configuration are the only workarounds. Authelia's random password generator will automatically output both
a normal version and a pre-encoded version which you could utilize.
Common Notes
- The OpenID Connect 1.0
client_id
parameter:- This must be a unique value for every client.
- The value used in this guide is merely for readability and demonstration purposes and you should not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
- This must only contain RFC3986 Unreserved Characters.
- This must be no more than 100 characters in length.
- The OpenID Connect 1.0
client_secret
parameter:- The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ.
- This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
- When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of hashing can, if too great, cause timeouts for clients. See the Tuning the work factors guide for more information.
- The configuration example for Authelia:
- Only contains an example configuration for the client registration and you MUST also configure the required elements from the OpenID Connect 1.0 Provider Configuration guide.
- Only contains a small portion of all of the available options for a registered client and users may wish to configure portions that are not part of this guide or configure them differently, as such it’s important to both familiarize yourself with the other options available and the effect of each of the options configured in this section by looking at the OpenID Connect 1.0 Clients Configuration guide.
Assumptions
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:
insecure_secret
Some of the values presented in this guide can automatically be replaced with documentation variables.
Configuration
Authelia
The following YAML configuration is an example Authelia client configuration for use with BookStack which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'bookstack'
client_name: 'BookStack'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
require_pkce: true
pkce_challenge_method: 'S256'
redirect_uris:
- 'https://bookstack.example.com/oidc/callback'
scopes:
- 'openid'
- 'profile'
- 'email'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
Application
To configure BookStack there is one method, using the Environment Variables.
Environment Variables
To configure BookStack to utilize Authelia as an OpenID Connect 1.0 Provider, use the following environment variables:
Standard
AUTH_METHOD=oidc
AUTH_AUTO_INITIATE=false
OIDC_NAME=Authelia
OIDC_ISSUER=https://auth.example.com
OIDC_ISSUER_DISCOVER=true
OIDC_CLIENT_ID=bookstack
OIDC_CLIENT_SECRET=insecure_secret
OIDC_ADDITIONAL_SCOPES=groups
OIDC_DISPLAY_NAME_CLAIMS=name
OIDC_GROUPS_CLAIM=groups
OIDC_USER_TO_GROUPS=true
OIDC_REMOVE_FROM_GROUPS=true
OIDC_END_SESSION_ENDPOINT=false
Docker Compose
services:
bookstack:
environment:
AUTH_METHOD: 'oidc'
AUTH_AUTO_INITIATE: 'false'
OIDC_NAME: 'Authelia'
OIDC_ISSUER: 'https://auth.example.com'
OIDC_ISSUER_DISCOVER: 'true'
OIDC_CLIENT_ID: 'bookstack'
OIDC_CLIENT_SECRET: 'insecure_secret'
OIDC_ADDITIONAL_SCOPES: 'groups'
OIDC_DISPLAY_NAME_CLAIMS: 'name'
OIDC_GROUPS_CLAIM: 'groups'
OIDC_USER_TO_GROUPS: 'true'
OIDC_REMOVE_FROM_GROUPS: 'true'
OIDC_END_SESSION_ENDPOINT: 'false'