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
Re-creating this issue as a Feature request instead of a Bug as requested.
I noticed that when I disable an account, whether through removing the user from the Emby LDAP group or simply checking the Disable account option in Emby for the user. They can still make requests using Jellyseerr.
Desired Behavior
I would expect the behaviour to be once the account is disabled in emby or by removing them from the ldap group, they are forcibly logged out so they can no longer access the Jellyseerr portal.
For use with LDAP, it would be a group check or something like that, once out of the group, the user can't access Emby anymore, so Jellyseerr could make a check every now and then to see if they are still in the LDAP group synced with Emby. If not in the group, auto disable and log the user out.
Additional Context
It would be nice to have some kind of option to disable the account in Jellyseerr if it can't sync with the Emby Devices.
Or a task to check if someone is disabled in Emby and if so, disable them in Jellyseerr, and when re-enabled, re-eneble it in Jellyseerr.
Code of Conduct
I agree to follow Jellyseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Re-creating this issue as a Feature request instead of a Bug as requested.
I noticed that when I disable an account, whether through removing the user from the Emby LDAP group or simply checking the Disable account option in Emby for the user. They can still make requests using Jellyseerr.
Desired Behavior
I would expect the behaviour to be once the account is disabled in emby or by removing them from the ldap group, they are forcibly logged out so they can no longer access the Jellyseerr portal.
For use with LDAP, it would be a group check or something like that, once out of the group, the user can't access Emby anymore, so Jellyseerr could make a check every now and then to see if they are still in the LDAP group synced with Emby. If not in the group, auto disable and log the user out.
Additional Context
It would be nice to have some kind of option to disable the account in Jellyseerr if it can't sync with the Emby Devices.
Or a task to check if someone is disabled in Emby and if so, disable them in Jellyseerr, and when re-enabled, re-eneble it in Jellyseerr.
Code of Conduct
The text was updated successfully, but these errors were encountered: