New Emby version preserving login if process is terminated

[TheShanMan 41]

I've always had a button on my remote mapped to kill and restart the Emby app as a "1 tap" way to log out. That was paired with keeping the "stay logged in" (don't remember the exact text) checkbox unchecked during login. Now that checkbox is gone and I can't seem to find a way to require logging in again if I hit my "restart" button (the new app didn't preserve my old config and needed to be set up from scratch so it's possible I missed something).

Granted, that was always a hacky way to achieve a "1 tap" log out. I don't want to go through menus (multiple button presses) to log out. Is there any way to achieve what I want, whether it's restoring the old functionality so my "restart" button works again as is, or mapping that button to a single key press that will tell the Emby app to log out without having to navigate or confirm, or worst case scenario, having that button show a confirmation prompt and tapping that same button a second time to confirm and log out?

Trying to be open to whatever options might achieve the goal while keeping the process brain-dead trivial for my family.

[Lessaj 506]

Why do you need to log out each time?

You could try setting General -> Startup behaviour to "Show login screen"

[TheShanMan 41]

Because I don't want logins to be persistent. I've tried that setting, but the login is saved so when you choose the user that was previously logged in, it doesn't request a pin again.

[softworkz 5236]

I don't think we have a built-in shortcut to do this, but if your remote allows to be programmed to send a sequence of key strokes, you could do something like

• CTRL-SHIFT-S (stop playback - in case)
• POS1 (go to home screen)
• UP UP UP RIGHT UP RIGHT RIGHT (get on the user menu)
• ENTER/OK
• DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN UP ENTER (sign out)
• ALT-F4 (close app)

 

[TheShanMan 41]

Upwards of 20 key presses? Seems error prone and hacky. Could I make it work? Yeah maybe. But it's way worse than what I used to be able to do. Why can't the existing behavior be maintained? And if it can't, how about adding an "immediate logout" key that could be mapped on a remote?

[TheShanMan 41]

Giving more thought, what is even the point of authentication in Emby if logging out takes 20 key presses? Is it just that the TV experience is not a priority for Emby? Is it that multi-user devices (TV being the primary example) isn't a priority? I don't really mean this to sound snarky. I'm legitimately curious now what the philosophy of authentication is for Emby these days.

[softworkz 5236]

1 hour ago, TheShanMan said:

Upwards of 20 key presses? Seems error prone and hacky.

I added more presses than are actually needed to make it resilient against differences and changes.

I think it's less hacky than it looks like. The key (key) is Pos1, which always brings you to the home view and then it's just getting to the menu. Going downmost first and then up is more safe than counting from the top, because there can be additional items in the menu, but from the bottom should be stable.

Anyway - it was meant as a quick remedy only. If you want to discuss better ways, that's fine and I actually DO think we should have a way to do this more easily. 

 

1 hour ago, TheShanMan said:

But it's way worse than what I used to be able to do.

I don't agree to this, because this is a supported method and killing the app is not a good idea at all, because the app is doing a number of things on regular close which doesn't happen when you kill it.

 

1 hour ago, TheShanMan said:

Why can't the existing behavior be maintained? 

If you are asking why it doesn't continue to "forget" the login when killing, then that's really not something that can be called "a behavior".

 

But if you are asking why there is no way to require a login on each new app start - that's for @Luke to answer.

 

I'm not familiar with the PIN feature, but when you say it doesn't ask you on each start then that's at least in contradiction to the description text of the server:

 

@Luke- Is the user missing something? (or the app?)