This article explains the reasons you might be logged out of Signals Notebook and how different timeout settings work.
Why does Signals Notebook log me out?
Signals Notebook uses multiple timeout settings to ensure security and session management. The first timeout that applies will log you out. Here’s how they work:
Administrator-Defined Timeout
- Your system administrator can set a timeout in the Signals Notebook admin screen.
- This timeout applies if you are inactive in the user interface for longer than the set duration.
- Inactivity means no cursor movement or interaction in the browser window where Signals Notebook is open.
- Example: If the admin sets a 15-minute timeout and you don’t move your cursor for 15 minutes, you will be logged out.
2. Server-Enforced Timeout (30 minutes)
- Signals Notebook servers enforce a fixed 30-minute timeout that cannot be changed by administrators.
- This timeout applies if no data is sent from your browser to the Signals Notebook servers for 30 minutes.
- Example: If you are viewing a dashboard, Advanced Search, or a smart folder, the user interface does not continually check for updates. In this case, you will be logged out after 30 minutes of inactivity.
3. External Authentication (IdP) Timeout
- If your organization uses an external identity provider (IdP) for authentication (e.g., Single Sign-On), that system may enforce its own session timeout.
- If your IdP session expires, you may be prompted to re-authenticate, even if you are still logged into Signals Notebook.
- Conversely, if Single Sign-On (SSO) is enabled, the IdP may automatically log you back into Signals Notebook after a timeout.
What Counts as Activity?
Your activity in Signals Notebook determines which timeout applies:
| Scenario | Effect on Timeout |
|---|---|
| Viewing an experiment | The user interface continually checks for updates, keeping the server session active. You will only be logged out if you exceed the admin-defined timeout for inactivity. |
| Viewing a dashboard, Advanced Search, or smart folder | The user interface does not check for updates. You will be logged out after 30 minutes of inactivity. |
| Computer goes to sleep | The 30-minute server timeout applies, as no data is sent to the server. |
| Signals Notebook is not the active browser window | The 30-minute server timeout applies, as no data is sent to the server. |
How to Avoid Unexpected Logouts
- Move your cursor periodically if you are actively working in Signals Notebook.
- Save your work frequently to avoid losing progress.
- Check with your administrator to confirm the timeout settings for your organization.
- If you use an external IdP, be aware of its session policies, as they may affect your login status.
Frequently Asked Questions
Why was I logged out even though I was working?
- If you were viewing a dashboard or a smart folder, the 30-minute server timeout may have applied.
- If your computer went to sleep or Signals Notebook was not the active browser window, the server session may have expired.
Can I change the timeout settings?
- The 30-minute server timeout cannot be changed.
- The administrator-defined timeout can be adjusted by your system administrator.
Why do I sometimes get logged back in automatically?
- If your organization uses Single Sign-On (SSO), your IdP may automatically log you back into Signals Notebook after a timeout.
Comments
0 comments
Article is closed for comments.