Q1 - Description
Sometimes with new versions of passbolt and/or browser plugin there is a new behavior against the time periods for reasking the personnel password. (At the moment passbolt asks very more often than in the past - it is absolutely annoying at this moment!)
Please provide the possibility to control that behavior from the server like the settings for email notifications.
While searching for a solution the reference for variables found here: https://help.passbolt.com/configure/reference
But there is no clarification where and how to set and how to ask the actual values. The “PASSBOLT_AUTH_TOKEN_EXPIRY” (3 days) does not work
Q2 - Who is impacted?
- all Administrators
- all Users
Q3 - Why is it important and/or urgent?
Password reasking:
Maybe Your opinion against this behavior changes from time to time - but Your customers have an own opinion and they would have the control about it
Documentation of variables:
A documentation against anything are only helpfull if it is useable in practice. Please let use not die unknowing how the provided bits to use without deeper study of github source code and so on (Here https://github.com/passbolt/passbolt_docker described that the variable are relavant for docker + https://github.com/passbolt/passbolt_api/blob/master/config/app.default.php + https://github.com/passbolt/passbolt_api/blob/master/config/default.php) - but all of this is for development familiar people - not for customers of a (Your!) product.)
Q4 - What is your proposed solution? (optional)
A good solution from my point of view is to integrate the mentioned aspects as part of the http(s)://./app/administration site as one or two new subpages
If it is not possible for technical reasons for the general parameters provide a comprehensive and applicable documentation for administrators
Q5. Community support
People can vote for this idea to show traction:
-
Must have: this is critical for me to have this -
Should have: this is important for me to have this -
Could have: this could be nice to have -
Won’t have: we should not schedule this (explain why)
0 voters