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
Due to issues with giving external plex users access to my libraries, I simply share my plex password with them.
Of course, this is a bad idea in theory but in practice the sharing functionality is a bit borked in my experience.
I would like to disable PlexOAuth and have all my users access Overseerr with local accounts I have set up for them, rather than have someone accidentally use PlexOAuth one day and not realise they have admin permissions, potentially breaking something.
As long as there's a local account with admin permissions to take over from the plex admin, this should not be an issue.
Of course, this can be done by manually editing the database entries with SQL, but I'm hoping this can be exposed as a feature in the webUI.
Desired Behavior
Option to disable plexOAuth once connection has been made, and a local account with admin permissions has been created.
Additional Context
I guess the reason PlexOAuth is preferred is so you dont have to deal with anyone forgetting their passwords and getting locked out of the UI, but honestly if it comes to it, I can reinstall the container or whatever. Being a sysadmin has some privileges in that regard.
Code of Conduct
I agree to follow Overseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Due to issues with giving external plex users access to my libraries, I simply share my plex password with them.
Of course, this is a bad idea in theory but in practice the sharing functionality is a bit borked in my experience.
I would like to disable PlexOAuth and have all my users access Overseerr with local accounts I have set up for them, rather than have someone accidentally use PlexOAuth one day and not realise they have admin permissions, potentially breaking something.
As long as there's a local account with admin permissions to take over from the plex admin, this should not be an issue.
Of course, this can be done by manually editing the database entries with SQL, but I'm hoping this can be exposed as a feature in the webUI.
Desired Behavior
Option to disable plexOAuth once connection has been made, and a local account with admin permissions has been created.
Additional Context
I guess the reason PlexOAuth is preferred is so you dont have to deal with anyone forgetting their passwords and getting locked out of the UI, but honestly if it comes to it, I can reinstall the container or whatever. Being a sysadmin has some privileges in that regard.
Code of Conduct
The text was updated successfully, but these errors were encountered: