Sessions
The session settings are per project, in the configuration editor under Users › Policies.
Session settings
| Setting | Default | Range in the form | Meaning |
|---|---|---|---|
| Access lifetime (minutes) | 15 | 5–60 | How long one access token is valid. The browser renews it in the background. |
| Refresh lifetime (hours) | 8 | 1–24 | How long the token used for renewal is valid. |
| Idle timeout (minutes, 0 = none) | 30 | 0–480 | The session ends after this long without activity. |
| Logout warning (seconds before, 0 = none) | 60 | 0–600 | A countdown is shown this long before an idle sign-out. It cannot exceed half of the idle timeout. |
Login notice
Login notice is a text shown in the login window, for example that unauthorised use is forbidden and that actions are recorded. Leave it empty to show nothing. With Require acceptance before login, users must tick the notice before they can sign in; the server refuses a sign-in without it.
The root session
The root account has its own session settings, with the same defaults; they are not changed in a project. Root signs in once per browser: the editors opened from the home page and the other YTCC tabs of the browser take over the session, a reload keeps it, and Exit in a tab where root is in effect ends it in every tab. A tab where a project user signed in, or that signed in automatically, keeps its own session. The idle timeout ends the session of the idle tab only. See Root, the system administrator.
Automatic sign-in
Automatic sign-in opens a session for a fixed user without the login window. It is an installation setting
(YTCC_AUTO_LOGIN_USER), off by default, and meant for development. It works only for a browser on the server itself,
and every automatic sign-in is written to the audit log.
In an automatic session, commands to the field require a real sign-in. Alarms can still be acknowledged. An automatic session never counts as root, and a tab that signed in automatically does not take over root from another tab.
Do not turn on automatic sign-in on a site installation. Anyone at the server's screen would work as that user.