add callback uri for oidc auth to documentation, also add screenshots of Authentik and PocketId configuration

This commit is contained in:
maxDorninger
2025-07-31 14:25:57 +02:00
parent 1862707ae3
commit 405f807c1e
3 changed files with 31 additions and 1 deletions

View File

Binary file not shown.

After

Width:  |  Height:  |  Size: 125 KiB

View File

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

View File

@@ -49,12 +49,42 @@ Client secret provided by your OpenID Connect provider.
- `configuration_endpoint`
OpenID Connect configuration endpoint URL. Note the lack of a trailing slash - this is important.
OpenID Connect configuration endpoint URL. Note the lack of a trailing slash - this is important. It usually ends with
`.well-known/openid-configuration`.
- `name`
Display name for the OpenID Connect provider that will be shown on the login page.
### Configuration for your OpenID Connect Provider
#### Redirect URI
The OpenID server will likely require a redirect URI. The exact path depends on the `name` of the OIDC provider. Note
that the `name` is case-sensitive.
```
{FRONTEND_URL}/api/v1/auth/cookie/{OPENID_NAME}/callback
```
E.g.: I use `Authentik` as the `name`, thus the redirect URI would be:
```
https://mediamanager.example.com/api/v1/auth/cookie/Authentik/callback
```
#### Authentik Example {collapsible="true"}
Here is an example configuration for the OpenID Connect provider for Authentik.
![authentik-example-config.png](authentik-example-config.png)
#### PocketID Example {collapsible="true"}
Here is an example configuration for the OpenID Connect provider for PocketID.
![pocketid-example-config.png](pocketid-example-config.png)
## Example Configuration
Here's a complete example of the authentication section in your `config.toml`: