Title: Enable SAML-Authenticated Sessions to persist past Browser restart
1) What is your original issue/pain point you want to solve?
The user is required to login again after closing the browser if they authenticated using SAML.
This behaviour may be present in other authentication methods (see related posts).
2) Which are one or two concrete situations where this problem hurts the most?
This behaviour introduces an additional point of friction to the login process. While I acknowdlege that this friction is relatively minor, in daily use this nonetheless has the potential to add up.
3) Why is it not solvable with the Zammad standard?
I was unable to locate a setting to modify this behaviour.
As such, until proven otherwise, this is not solvable.
4) What is your expectation/what do you want to achieve?
I propose the addition of a Setting similar to the “Remember Me” checkbox used in the native login process. This would modify the session (cookie?) to persist past browser restarts.
Related Posts:
- SAML-Authenticated Sessions do not persist on Browser restart
- Zammad re-login required when closing browser (Google Auth)
Your Zammad environment:
- Average concurrent agent count: 3
- Average tickets a day: 20
- What roles/people are involved: IT and Application Groups (Agent), Users