title = "BookStack"
baseurl = "https://bookstackapp.com/"
theme="bookstack"
+enableGitInfo=true
[permalinks]
post = "/blog/:slug/"
BookStack has similar requirements to Laravel:
-* PHP >= 5.6.4, Will need to be usable from the command line.
+* PHP >= 7.0.0, Will need to be usable from the command line.
* PHP Extensions: `OpenSSL`, `PDO`, `MBstring`, `Tokenizer`, `GD`, `MySQLND`, `Tidy`
* MySQL >= 5.6, Single DB *(All permissions advised since application manages schema)*
* Git *(Not strictly required but helps manage updates)*
+++
-title = "Social Authentication"
-description = "Enabling and configuring social authentication for easier logins"
+title = "Third Party Authentication"
+description = "Enabling and configuring third-party authentication for easier logins"
date = "2017-01-01"
type = "admin-doc"
+aliases = [
+ "/docs/admin/social-auth"
+]
+++
-BookStack currently supports login via Google, Facebook, Slack, Twitter & GitHub. 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 require application id's and secrets. Here are instructions to do this for the current supported services:
+BookStack currently supports login via Google, Facebook, Slack, Twitter, GitHub, AzureAD and Okta. 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 require application id's and secrets. Here are instructions to do this for the current supported services:
---
APP_URL=http://mybookstackurl.com
```
10. All done! Users should now be able to link their AzureAD account in their account profile pages and also register/login using their Slack account.
+
+---
+
+### Okta
+
+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. These are your 'APP_ID' and 'APP_SECRET' values for step 6.
+6. Copy these details and add them as new variables in your `.env` file like so:
+ ```bash
+ # Replace the below (including '{}' braces) with your okta APP_ID and APP_SECRET and BASE_URL.
+ OKTA_APP_ID={APP_ID}
+ OKTA_APP_SECRET={APP_SECRET}
+ # The base URL is the URL from step 1 but with everything after the domain (okta.com) removed.
+ OKTA_BASE_URL={BASE_URL}
+
+ # APP_URL Needs to be set to your BookStack base url
+ APP_URL=http://mybookstackurl.com
+ ```
+7. 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.
\ No newline at end of file
## Version Specific Instructions
+#### Updating to v0.19 or higher
+
+Version v0.19 needs the following requirement change:
+
+* Minimum required version of PHP has changed from 5.6.4 to 7.0.0.
+
#### Updating to v0.18 or higher
Version v0.18 introduced a commenting system. After updating you should check the permissions for all roles if you'd like to enable comments for your users.
+++
If you prefer the write in Markdown the editor in BookStack can be changed at a instance level
-to use a markdown editor instead of the default WYSIWYG editor.
-
-The option to use Markdown is currently **not** a user setting but a global instance setting
+to use a markdown editor instead of the default WYSIWYG editor. The option to use Markdown is currently **not** a user setting but a global instance setting
due to formatting differences between the two editors.
### Editor Shortcuts
<td><code>Ctrl+S</code> / <code>Cmd+S</code></td>
<td>Save Draft</td>
</tr>
+ <tr>
+ <td><code>Ctrl+Enter</code> / <code>Cmd+Enter</code></td>
+ <td>Save Page & Continue</td>
+ </tr>
<tr>
<td>
<code>Ctrl+1</code> / <code>Cmd+1</code> <br>
<td><code>Ctrl+S</code> / <code>Cmd+S</code></td>
<td>Save Draft</td>
</tr>
+ <tr>
+ <td><code>Ctrl+Enter</code> / <code>Cmd+Enter</code></td>
+ <td>Save Page & Continue</td>
+ </tr>
<tr>
<td><code>Ctrl+B</code> / <code>Cmd+B</code></td>
<td>Bold</td>
<meta property="og:type" content="article" />
<meta property="og:article:published_time" content="{{ .Date.Format "2006-01-02T15:04:05Z07:00" | safeHTML }}" />
+ <meta property="og:article:modified_time" content="{{ .Lastmod.Format "2006-01-02T15:04:05Z07:00" | safeHTML }}" />
{{ range .Params.tags }}
<meta property="og:article:tag" content="{{ . }}" />
<h4>Configuration</h4>
<ul>
<li><a href="/docs/admin/cache-session-config">Caching & Sessions</a></li>
- <li><a href="/docs/admin/social-auth">Social Authentication</a></li>
+ <li><a href="/docs/admin/social-auth">Third Party Authentication</a></li>
<li><a href="/docs/admin/ldap-auth">LDAP Authentication</a></li>
<li><a href="/docs/admin/pdf-rendering">PDF Rendering</a></li>
<li><a href="/docs/admin/ut8mb4-support">UTF8mb4/Emoji Support</a></li>
projects / website / commitdiff