Explains what Portal login timeouts are and when they occur.
What is a "Timeout"?
A timeout is a period of time after which a software system, such as the Portal, will require that a user be re-authenticated in order to continue his/her session.
Authentication is when a software system verifies that the user is who they claim to be. Authentication in the Portal initially occurs manually when a user logs in with his/her login credentials (username and password). Re-authentication in the Portal after a timeout period can also occur automatically (meaning the user is not required to re-enter his/her credentials).
A session is the period of activity between when a user is initially authenticated and when that user logs out, during which time the system "knows" who that user is.
When a timeout period elapses and a user must be re-authenticated, this event is referred to as the session "timing out".
Why Do I Care About Timeouts?
There are several underlying processes that support the Portal, and a small number of these have their own timeout periods. When a user's session times out after one of these periods, there are certain consequences depending on which process's timeout period it was.
The following are the timeouts that Content Managers should be aware of:
- Your session will time out 8 hours after you initially log in, and you will be required to re-enter your login credentials. This timeout will occur again after another 8 hours. If you are working on changes to Portal content when this timeout occurs, any unsaved changes you have made will be lost, so be mindful of your last login time when you begin editing content.
- When working on changes to Portal content, you must save your work within 2 hours of the time you began, otherwise any unsaved changes made during that 2 hour period will be lost.