diff options
| author | mrdrogdrog | 2020-11-15 13:19:39 +0100 |
|---|---|---|
| committer | GitHub | 2020-11-15 13:19:39 +0100 |
| commit | 03795cbf7ba5809751da1e2366abd5a3a653c9f2 (patch) | |
| tree | d95fbb52d1829ede0068a77192186faaacf46ce0 /docs/guides | |
| parent | d2e4afb77e51d363453928a972c9e42d5182bf97 (diff) | |
Update docs/guides/auth/keycloak.md
Co-authored-by: Philip Molares <git@molar.es>
Diffstat (limited to 'docs/guides')
| -rw-r--r-- | docs/guides/auth/keycloak.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/guides/auth/keycloak.md b/docs/guides/auth/keycloak.md index 8f85d721..82f6d321 100644 --- a/docs/guides/auth/keycloak.md +++ b/docs/guides/auth/keycloak.md @@ -24,7 +24,7 @@ You may note that a separate realm is specified throughout this tutorial. It is 1. Select Client Scopes from the sidebar, and begin to create a new client scope using the Create button. 2. Ensure that the **Name** field is set to `id`. 3. Create a new mapper under the Mappers tab. This should reference the User Property `id`. `Claim JSON Type` should be String and all switches below should be enabled. Save the mapper. -4. Go to the client you set up in the previous steps using the Clients page, then choose the Client Scopes tab. Apply the scope you've created. This should mitigate errors as seen in [hedgedoc/server#56](https://github.com/hedgedoc/hedgedoc/issues/56), as the `/userinfo` endpoint should now bring back the user's ID under the `id` key as well as `sub`. +4. Go to the client you set up in the previous steps using the Clients page, then choose the Client Scopes tab. Apply the scope you've created. This should mitigate errors as seen in [hedgedoc/hedgedoc#56](https://github.com/hedgedoc/hedgedoc/issues/56), as the `/userinfo` endpoint should now bring back the user's ID under the `id` key as well as `sub`. --- |