Feature Request - Cache Authorized User Access Token Session

[Sn3akyP3t3]

MWB doesn't seem to have any notion of a session when it comes to prompting for User Access Password.  This can be annoying when the location of a particular feature is not known and the password is prompted for every different subsection that is accessed, no matter if that subsection has been accessed previously or not.  If a session variable is set for a timeout then the prompting can be enabled after X minutes with no activity.  If you want a software title that does this fairly well as an example check out Keepass.  The password database will lock in X seconds where the value X is user customizable.  The lock can also be re-enabled when the user logs out, locks the screen, or perhaps with some other triggers useful for presence detection (perhaps Android phone Windows stuffs that I'm not familiar with).

[Sn3akyP3t3]

When the User Access feature is enabled the password is prompted when trying to access any of the protected sections it is applied to which is desired, but it does it for EVERY movement between sections (tabs) that are protected.  There should be some notion of a session where you are prompted only once for the credentials at which time they are cached for the duration of your activity with the MWB UI opened and as soon as the MWB UI is closed the session expires and the password prompt is enabled once again.

Providing the password multiple time when reviewing or changing settings is a huge irritation!

[Sn3akyP3t3]

Oops, apparently I forgot I had already posted this and recreated it in another new thread...

 

[exile360]

Thanks for pointing this out, I knew that request sounded familiar

[AdvancedSetup]

Thank you for your feedback @Sn3akyP3t3 I have passed  your information along to the internal development team

 

[AdvancedSetup]

I have merged the posts into this same topic

Thank you again