Seerr
Seerr
This integration guide is community supported. It's not guaranteed to be complete, accurate, or up-to-date. It's likely that if this integration guide does not work for you that changes occurred with a third-party application.
Important Note: This documentation is version specific. Make sure you check the section outlining the tested versions.
Important Note: We always recommend users read the third-party documentation as part of the integration process to ensure configuration elements matches their needs. As such the See Also section is likely to have important links.
Important Note: If you find an error in this documentation please make a Pull Request, start a Discussion, or contact us on a Chat Room.
Introduction
This is a guide on integration of Authelia and Seerr via the trusted header SSO authentication.
As with all guides in this section it’s important you read the introduction first.
Tested Versions
- Authelia:
- v4.39.18
- Seerr Server
Before You Begin
This example makes the following assumptions:
- Application Root URL:
https://seerr.example.com/ - Authelia Root URL:
https://auth.example.com/ - User Email Domain:
@example.com - Seerr has been initialized already with a user to configure this. Trusted header SSO cannot be used to auto-create users.
- Trusted header SSO can only be used when trust proxy is enabled.
- This feature will only work if a list of trusted proxies is provided.
Some of the values presented in this guide can automatically be replaced with documentation variables.
Configuration
To configure Seerr to trust the Remote-User and Remote-Email header do the following:
With GUI
- Login as an admin user.
- Navigate to Settings -> Network.
- Enable “Trust Proxy”
- Provide a list of trusted proxies in Advanced Network Settings.
- Select
remote-userandremote-emailfrom the list. Seerr will look for both fields in requests if they are configured here.
Alternatively, you can select just the username and look for only the username in the requests.
- Save changes.
Editing the configuration directly
Update the configuration file to this
...
"network": {
...
"trustProxy": true,
"trustedProxies": {
"v4": [
"10.0.50.3"
],
"v6": [
"fd00:dead::beef"
]
},
"forwardAuth": {
"enabled": true,
"userHeader": "remote-user",
"emailHeader": "remote-email"
},
"proxy": {
...The header names in the GUI and config file are case insensitive.