You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Jellyseerr only supports password based authentication. While full OIDC support is in the works, as seen in the roadmap, it could be nice to support Forward Auth. Which would enable users to use their existing SSO with minimal effort.
Desired Behavior
When checking the authentication upon page load, check whether the request contains a certain header (i.e X-authentik-username), which should be predefined or configurable in settings. Jellyseerr can trust that the header contains the username of an authenticated user. The general flow of new user/first admin/... can follow the current flow of a new Jellyfin user.
Additional Context
I would be willing to work on this, but first want to validate whether this is a contribution you would be willing to accept!
Code of Conduct
I agree to follow Jellyseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Currently Jellyseerr only supports password based authentication. While full OIDC support is in the works, as seen in the roadmap, it could be nice to support Forward Auth. Which would enable users to use their existing SSO with minimal effort.
Desired Behavior
When checking the authentication upon page load, check whether the request contains a certain header (i.e X-authentik-username), which should be predefined or configurable in settings. Jellyseerr can trust that the header contains the username of an authenticated user. The general flow of new user/first admin/... can follow the current flow of a new Jellyfin user.
Additional Context
I would be willing to work on this, but first want to validate whether this is a contribution you would be willing to accept!
Code of Conduct
The text was updated successfully, but these errors were encountered: