The guest account ‘feature’ as of 1.13.2.5154 still just doesn’t work for me, I have read through a few of the threads on this and to me it seems that with a little adjustment it would work better.
My use case is that I have a lot of kids that come over to the house that dont (or shouldn’t) have email/google/fb credentials and honestly I just want them to go to an easy FQDN and get access to cartoons and whatnot. Right now, you HAVE to log into a plex web account of some sort BEFORE you get to that server list. I don’t want to create a “household guest email account or FB page” to accommodate this…
The logic probably needs to be reviewed a bit more but it doesn’t seem that hard to make the feature adjustments.
- Enable Guest account (as you do now with a button)
- Configure restrictions if you desire (feature add: Allow for an optional PIN)
- When a user attempts to connect to https://:32400 a. Check if the request is from the LAN or if it is remote. b. If it is remote, i. Redirect to https://app.plex.tv/auth and force a login with their plex web account. ii. If plex web login is successful, present the user list. Display guest if allowed [CONFIG OPTION TO ALLOW GUEST REMOTE] iii. Process login and apply ACLs c. If it is local/LAN, Check if guest is enabled on the server. i. GUEST ENABLED: redirect to https://app.plex.tv/auth with a cookie or parameter that allows guest login, present plex web sign in page with an option to “SIGN IN AS GUEST” in addition to google/fb/email, and if the “SIGN IN AS GUEST” button is selected then redirect back to the server and login as the guest user ONLY. If the guest button is NOT selected, then return to the server with the list of users on the server as it does today. ii. GUEST DISABLED: redirect to https://app.plex.tv/auth as it does today so they login with a their plex web account and then get redirected back to the user list on the server. d. Lastly, allow for a pin to be created for the guest user.
Thanks for the consideration…
