Admin Documentation

Third Party Authentication

BookStack currently supports login via a range of third party and social applications. Once enabled options for these services will show up in the login, registration and user profile pages. By default these services are disabled. To enable them you will have to create an application on the external services to obtain the required application credentials.

Available Services

Automatic Registration

You may find that you’d like to auto-register users, from the login screen, when they use a social authentication option. To do this add the following .env option, altering the {SERVICE} to match the login service you are using:

1
2
3
4
5

{SERVICE}_AUTO_REGISTER=true

# Examples
GOOGLE_AUTO_REGISTER=true
TWITCH_AUTO_REGISTER=true

This will allow registration using these services even if registrations are disabled. It also allows registration if using LDAP as your main authentication option.

Automatic Email Confirmation

If you trust a third-party login service you can enable automatic email confirmation. This skips the ‘Confirm Email’ setting, even if domain restrictions are enabled although the domain of the email address provided by the social service will still be checked. To do this add the following .env option, altering the {SERVICE} to match the login service you are using and trust:

1
2
3
4
5

{SERVICE}_AUTO_CONFIRM_EMAIL=true

# Examples
GOOGLE_AUTO_CONFIRM_EMAIL=true
TWITCH_AUTO_CONFIRM_EMAIL=true

Google

  1. Open the Google Developers Console.
  2. Create a new project (May have to wait a short while for it to be created).
  3. In ‘API and Services’ go to the ‘OAuth consent screen’ section and enter a product name (‘BookStack’ or your custom set name) along with any other required details until you can save your consent screen.
  4. Now in the ‘API and Services’ > ‘Credentials’ section click ‘Create Credentials’ > ‘OAuth client ID’.
  5. Choose an application type of ‘Web application’ and enter the following urls under ‘Authorized redirect URIs’, changing https://example.com to your own domain where BookStack is hosted:
    • https://example.com/login/service/google/callback
    • https://example.com/register/service/google/callback
  6. Hit ‘Create’ then take note of the ‘Client ID’ and ‘Client secret’ which you’ll use in the next step.
  7. Add or set the following items in your .env file like so:
1
2
3

# Replace the '{client_id}' and '{client_secret}' below with your Google Client ID and Client secret
GOOGLE_APP_ID={client_id}
GOOGLE_APP_SECRET={client_secret}
  1. All done! Users should now be able to link their social accounts in their account profile pages and also register/login using their Google accounts.

GitHub

  1. While logged in, open up your GitHub developer applications.
  2. Click ‘Register new application’.
  3. Enter an application name (‘BookStack’ or your custom set name) and a link to your app instance under ‘Homepage URL’. The ‘Authorization callback URL’ can be the root (homepage) URL for your BookStack instance. Once those details are set, select ‘Register application’.
  4. A ‘Client ID’ and a ‘Client Secret’ value will be shown. Add or set the following items in your BookStack .env file like so:
1
2
3

# Replace the '{client_id}' and '{client_secret}' below with your GitHub Client ID and Client secret
GITHUB_APP_ID={client_id}
GITHUB_APP_SECRET={client_secret}
  1. All done! Users should now be able to link their social accounts in their account profile pages and also register/login using their GitHub account.

Twitter

Before creating a Twitter application for signing in, you will need to have signed up and be approved on the Twitter Developer site. Part of this will require describing your use of the API.

  1. Go to your Twitter Developer Portal, after being approved by twitter as described above. Navigate to ‘Projects and Apps’ > ‘Overview’ and under ‘Standalone Apps’ click ‘Create App’.
  2. Enter an application name and save/continue to the next step.
  3. You’ll now be shown some keys and tokens. Copy out the shown ‘API key’ and ‘API secret key’ values for the next step.
  4. Within your BookStack .env file add in extra options for your token and secret like so:
1
2
3

# Replace the below '{api_key}' and '{api_secret}' with your Twitter API key and API secret
TWITTER_APP_ID={api_key}
TWITTER_APP_SECRET={api_secret}
  1. Back within the Twitter developer dashboard, find your new standalone app and click on ‘App Settings’ then click on edit within the ‘Authentication settings’ section.
  2. Enable the ‘3-legged OAuth’ and ‘Request email address from users’ options.
  3. Enter the following URLs under ‘Callback URLs’, changing https://example.com to your own domain where BookStack is hosted:
    • https://example.com/login/service/twitter/callback
    • https://example.com/register/service/twitter/callback
  4. Fill in any remaining required URLs then click save.
  5. All done! Users should now be able to link their Twitter account in their account profile pages and also register/login using their Twitter account. You may want to review the other options for the Twitter Standalone app such as setting a logo and description.

Facebook

  1. Navigate to the Facebook developers page then go ‘My Apps’ -> ‘Add a New App’.
  2. Enter an app name (‘BookStack login’ or something custom) and contact email then continue.
  3. In your new app select ‘Add Product’ on the left sidebar then choose ‘Facebook Login’ by clicking the ‘Get Started’ button. Select the ‘Web’ option if asked to choose a platform.
  4. Enter the your base BookStack url into the ‘Site URL’ box and save.
  5. On the left sidebar again go to ‘Facebook Login’ -> ‘Settings’.
  6. Enter the following URLs under ‘Valid OAuth Redirect URIs’, changing https://example.com to your own domain where BookStack is hosted:
    • https://example.com/login/service/facebook/callback
    • https://example.com/register/service/facebook/callback
  7. Navigate back to the app ‘Dashboard’ in the sidebar to find your app id and secret. Add or set these to your .env file like so:
1
2
3

# Replace the below '{app_id}' and '{app_secret}' with your Facebook app ID and secret
FACEBOOK_APP_ID={app_id}
FACEBOOK_APP_SECRET={app_secret}
  1. All done! Users should now be able to link their Facebook account in their account profile pages and also register/login using their Facebook account.

Slack

  1. Go to the Slack apps page and select ‘Create An App’, then ‘From scratch’ when prompted.
  2. Enter an app name (‘BookStack login’ or something custom) and your workspace then select “Create App”.
  3. Within an “App Credentials” section, you should find your client ID and secret. Copy these details and add them as new variables in your .env file like so:
1
2
3

# Replace the below '{client_id}' and '{client_secret}' with your Slack client ID and secret
SLACK_APP_ID={client_id}
SLACK_APP_SECRET={client_secret}
  1. In your slack app go to ‘OAuth & Permissions’, find the ‘Redirect URLs’ section then ‘Add New Redirect URL’. Enter your BookStack base URL then ‘Add’ before pressing ‘Save URLs’.
  2. All done! Users should now be able to link their Slack account in their account profile pages and also register/login using their Slack account.

AzureAD (Microsoft)

Note: If you intend all users to access your instance via Azure, then using an alternative primary authentication option like OIDC or SAML 2.0 will provide a better user experience while having more features like auto-login and group sync. A video guide for setting up OIDC with AzureAD can be found here.

  1. Login to your your azure portal and navigate to the ‘Azure Activity Directory’ area.
  2. Under ‘Manage > App registrations’ select ‘New application registration’.
  3. Enter a name (‘BookStack’). Set the ‘Redirect URI’ to the “Web” platform with the value set to the following, replacing ‘https://example.com/' with your base BookStack url:
    • https://example.com/login/service/azure/callback
  4. Once created, View the application ‘Overview’ page and note the ‘Application (client) ID’ and ‘Directory (tenant) ID’ values. These are the APP_ID and TENANT values for step 9.
  5. Within your application in azure, Navigate to ‘Certificates & secrets’ then choose ‘New client secret’.
  6. Enter any description you want and set an expiry duration. Then click ‘Save’.
  7. Copy the string of characters under ‘Value’. This is the APP_SECRET value for step 9 and is only shown once.
  8. Navigate to ‘API permissions’ for your app. You should already have a “Microsoft Graph” > “User.Read” permission assigned. If not choose ‘Add a permission’. Find the ‘Microsoft Graph’ option within this, then select ‘Delegated permissions’ then find & select the ‘User.Read’ permission. Then select ‘Add permissions’ at the bottom of the page.
  9. Copy these details and add them as new variables in your .env file like so:
1
2
3
4

# Replace the below '{APP_ID}', '{APP_SECRET}' and '{TENANT}' values with your Azure APP_ID and APP_SECRET and TENANT
AZURE_APP_ID={APP_ID}
AZURE_APP_SECRET={APP_SECRET}
AZURE_TENANT={TENANT}
  1. All done! Users should now be able to link their AzureAD account in their account profile pages and also register/login using their AzureAD account.

Okta

Note: If you intend all users to access your instance via Okta, then using an alternative primary authentication option like OIDC or SAML 2.0 will provide a better user experience while having more features like auto-login and group sync.

  1. Login to Okta and, once logged in, Note the current URL. This is used for the ‘base_url’ in step 6.
  2. Navigate to the Admin panel then ‘Applications’ then select ‘Add Application’. Then select ‘Create New App’ on the left.
  3. For the ‘Platform’ choose ‘Web’. For the ‘Sign on method’ choose ‘OpenID Connect’ then click ‘Create’.
  4. Give the app a name such as ‘BookStack’ or ‘Our documentation’. Under the ‘Login redirect URIs’ option add both of the below URLs, Changing https://example.com to the base URL of your BookStack instance:
    • https://example.com/login/service/okta/callback
    • https://example.com/register/service/okta/callback
  5. Save and scroll down to the ‘Client Credentials’ area. Copy the ‘Client ID’ and ‘Client secret’ values for the next step.
  6. Copy these details and add them as new variables in your .env file like so:
1
2
3
4
5
6

# Replace the below '{client_id}' and '{client_Secret}' with your Okta client ID and secret
OKTA_APP_ID={client_id}
OKTA_APP_SECRET={client_secret}
# Replace the '{base_url}' below with the URL from step 1
# but with everything after the domain (okta.com) removed.
OKTA_BASE_URL={base_url}
  1. All set up! Remember to assign the new application you created in Okta to your Okta users otherwise they will not be able to register/login using the service.

GitLab

GitLab authentication works for both gitlab.com and self-hosted GitLab instances.

  1. Login to GitLab and go to your user settings.
  2. In the left sidebar select ‘Applications’.
  3. Set a name to identify the application, such as ‘BookStack Authentication’, and in the ‘Redirect URI’ input add both of the below URLs, Changing https://example.com to the base URL of your BookStack instance:
    • https://example.com/login/service/gitlab/callback
    • https://example.com/register/service/gitlab/callback
  4. Select the checkbox for the read_user scope.
  5. Press ‘Save application’. You will be shown the application ID and secret which you’ll need for the next step.
  6. Copy the below details and add them as new variables in your .env file like so:
1
2
3
4
5
6
7

# Replace the below '{app_id}' and '{app_secret}' with your GitLab application ID and secret values.
GITLAB_APP_ID={app_id}
GITLAB_APP_SECRET={app_secret}

# ONLY REQUIRED FOR SELF-HOSTED GITLAB INSTANCES - REMOVE FOR GITLAB.COM
# The below needs to match the base URI of your GitLab install, including the trailing slash.
GITLAB_BASE_URI=http://my-custom-gitlab.example.com/
  1. All set up! Users will now be able to use GitLab to sign-in and register.

Twitch

To allow Twitch sign-in you’ll first need to create an application from the Twitch developer site. Here’s the process:

  1. Login into the Twitch developer website.
  2. Navigate to your ‘Dashboard’ then ‘Apps’ and select ‘Register Your Application’.
  3. Set a name to identify the application, such as ‘BookStack Authentication’, and in the ‘OAuth Redirect URI’ input add the below URL, Changing https://example.com to the base URL of your BookStack instance:
    • https://example.com/login/service/twitch/callback
  4. Under the ‘Application Category’ option select ‘Website Integration’ then hit ‘Register’.
  5. Click the ‘New Secret’ button and accept the prompt that appears. You should now see both a ‘Client ID’ and ‘Client Secret’ value which you’ll use in the next step.
  6. Copy the below details and add them as new variables in your .env file like so:
1
2
3

# Replace the below '{client_id}' and '{client_secret}' with your Twitch client ID and secret values.
TWITCH_APP_ID={client_id}
TWITCH_APP_SECRET={client_secret}
  1. All set up! Users will now be able to use Twitch to sign-in and register.

Discord

To allow Discord sign-in you’ll first need to create an application on the Discord developer site. Here’s the process:

  1. Login into the Discord developer website.
  2. Select ‘Create an application’.
  3. Set a name to identify the application, such as ‘BookStack Authentication’, and save.
  4. In the sidebar, Open the OAuth2 settings for your application and add a redirect. Input the below URL, Changing https://example.com to be the base URL of your BookStack instance then save:
    • https://example.com/login/service/discord/callback
  5. Back in the ‘General Information’ section find the ‘Client ID’ and ‘Client Secret’ values which you’ll use in the next step.
  6. Copy the below details and add them as new variables in your .env file like so:
1
2
3

# Replace the below '{client_id}' and '{client_secret}' with your Discord client ID and secret values.
DISCORD_APP_ID={client_id}
DISCORD_APP_SECRET={client_secret}
  1. All set up! Users will now be able to use Discord to sign-in and register.
Edit this Page