Unable to update SESSION TIMEOUT value when PASSWORD EXPIRATION stores 180 or 365 days
Last updated 2022-02-10 ·Reference W-3550173 ·Reported By 3 users
Summary
When updating the field "Session times out after" while the field "User passwords expire in" is 180 days or One Year in Profile Base Session settings, "Session times out after" does not save.
Actual Results:
Unable to update “Session times out after” field when “User passwords expire in” stores “180 days” or “One year”.
Expected Behavior:
Able to update “Session times out after” field even if “User passwords expire in” stores “180 days” or “One year”.
Repro
1. Login
2. Open System Administrator profile
3. Click [Edit] button
4. Update “User passwords expire in” field
5. Click [Save] it.
Note: Please DO NOT update the both of “Session times out after” and “User passwords expire in” in same time.
In case of “180 days” or “One year”
1. Try to update “Session times out after” value (ex: From “2 hours” to “1 hour”)
2. You cannot update it. The value is reverted.
In case of “30 days”, “60 days”, “90 days” or “Never expires”
1. Try to update “Session times out after” value (ex: From “2 hours” to “1 hour”)
2. You can update it properly.
Workaround
Please update “User passwords expire in” ahead.
When “30 days”, “60 days”, “90 days” or “Never expires” are stored in “User passwords expire in” field, you can update "Session times out after" field properly.
After updating the value of "Session times out after" field, please revert “User passwords expire in” to “180 days” or “One year”.
Reported By (3)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.