authelia/docs/content/en/integration/openid-connect/bookstack/index.md

2.3 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
integration
parent
openid-connect
620 true true

Tested Versions

Before You Begin

{{% oidc-common %}}

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

Important Note: BookStack does not properly URL encode the secret per RFC6749 Appendix B at the time this article was last modified (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 1.0 Provider:

  1. Edit your .env file
  2. Set the following values:
    1. AUTH_METHOD: oidc
    2. OIDC_NAME: Authelia
    3. OIDC_DISPLAY_NAME_CLAIMS: name
    4. OIDC_CLIENT_ID: bookstack
    5. OIDC_CLIENT_SECRET: insecure_secret
    6. OIDC_ISSUER: https://auth.example.com
    7. OIDC_ISSUER_DISCOVER: true

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: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
  public: false
  authorization_policy: two_factor
  redirect_uris:
    - https://bookstack.example.com/oidc/callback
  scopes:
    - openid
    - profile
    - email
  userinfo_signing_algorithm: none

See Also