User Sessions
On this page
Each successful sign-in to Alloy Navigator starts a user session. The session record holds the account, the client IP address, the application the user signed in to, the logon time, and the time of the last activity. A session started through the REST API is recorded with an empty client IP address. Each session is also recorded in the User Sessions log.
Administrators see the active sessions, terminate them, and read the license seat use in two places: the User Sessions page of the Admin Center and the User Sessions node of the Settings App. How seats are licensed and activated is described in License Management.
When you change the license type, status, or roles on a technician account's form in the Settings App and click OK while that account has an active session, the Settings App shows "Your changes cannot be applied right now because there is an active session for this account. The new settings will be applied to the next session." To end the current session sooner, terminate it on a User Sessions page, in the Admin Center or in the Settings App, as described below.
Seat use
A license counts technicians in two ways, and one license can carry both:
| Seat type | What takes a seat |
|---|---|
| Named | Each active technician account with the named license type. The seat is taken by the account's existence. |
| Concurrent | Live sessions of a technician whose account has the concurrent license type, counted in one application per account as described below. A session is live while it has not ended and has responded within the last five minutes. |
Either count can be unlimited. Self Service Portal customer accounts are outside both counts. The reserved support account is outside the counts too, and it is given a session without any seat check.
- A named account can have one session per application at a time.
- A concurrent account can have several sessions. Two live sessions of one technician in the same application take two concurrent seats; sessions of one technician in different applications take at most one. Only the sessions in the application where the account has the most session records are counted.
- The concurrent limit is checked when a session starts. When the license has concurrent seats, any number of concurrent accounts can exist.
- When more active named technician accounts exist than the license allows, the Web App and the REST API refuse sign-in to everyone except a Web App administrator; see License Management.
- When you sign in to the Admin Center directly with a login and password, that session is opened outside named and concurrent seat counting. This direct sign-in cannot check a password that is still stored in the legacy form of an earlier version; the next successful sign-in to another application converts that password.
- When the Admin Center is opened from a signed-in Web App session, the Web App passes it a single-use code, and the Admin Center uses that Web App session. When the Web App session has a license error, the Web App passes a code that is accepted until one minute after it was issued instead, and the Admin Center is opened outside seat counting, as with a direct sign-in.
The Admin Center and the Settings App compute the Named Users row of their license usage panels differently, so the two can show different figures for the same license. Each panel is described below.
What a sign-in leaves behind
The sign-in result
Checking the credentials and starting the session are separate steps, so valid credentials can still fail to produce a session. A sign-in ends in one of four ways:
| Result | When | What the user sees |
|---|---|---|
| Signed in | A session was started. | The user is signed in. |
| Another session can continue | The account already has a session in this application, and the license has room for another. | A prompt that offers to continue or to disconnect the other session, and names the other session's IP address. |
| Another session must end | A named account already has a session in this application, whatever the seats; or a concurrent account has one and no further seat is available. | The user can continue only by ending the other session. |
| Refused | No seat is available at all. | The sign-in is refused. |
When no concurrent seat is available, the Web App refuses the sign-in with "Access to Alloy Navigator is denied because the license limit has been exceeded. Please contact your Alloy Navigator administrator." The REST API, the sign-in path that the Mobile App also uses, refuses it with "Access to Alloy Navigator is denied because the limit of concurrent sessions has been exceeded. Please contact your Alloy Navigator administrator." The Settings App refuses it with the same text as the REST API.
When the concurrent limit refuses a sign-in
A user who is refused at the concurrent limit can sign in once a concurrent seat is free, or can contact the administrator. To free concurrent seats or add more, the administrator can:
- Terminate sessions that are no longer needed on a User Sessions page, in the Admin Center or in the Settings App. A terminated session no longer takes a concurrent seat.
- Turn on the automatic termination of idle sessions of concurrent accounts, in the Admin Center or in the Settings App.
- Add concurrent seats by applying a license with a larger number of concurrent users; see License Management. Under a Cloud license, the License Management pages show the license without the controls that update it.
- Change the license type of a concurrent account to named: in the Admin Center, Named user under License Assignment on the account's General tab; in the Settings App, Named User in the account's License group. The named choice is unavailable when no named seat is left. See Create and Maintain Technician Accounts.
The session record
A successful sign-in creates a session record. If the application restarts while the record is still live, the user's session is resumed from the record instead of requiring a new sign-in.
How a session ends
| End | What happened |
|---|---|
| Sign-out | The user signed out. |
| Idle timeout | A concurrent account's session reached the idle limit, when automatic termination of idle sessions is turned on. |
| Terminated by an administrator | An administrator terminated the session. |
| Disconnected | The session was disconnected, or it had not responded for more than five minutes and was cleaned up. |
| Replaced by a new sign-in | A new sign-in of the same account in the same application ended the other session. |
The idle timeout applies to concurrent accounts only. A named technician's session does not time out on inactivity.
What the user sees in the Web App
The Web App checks the state of the session at the user's next page, link, or request, at most once a minute:
- A session that an administrator terminated ends with "Your Alloy Navigator session has been terminated by the administrator."
- A session that a new sign-in of the same account replaced ends with "Your account is being used to access Alloy Navigator from another computer. The concurrent session was established for a computer with the IP address ... Your session will be terminated.", naming the IP address of the new session.
- A session whose record is gone is restored when a seat allows. If it cannot be restored, the Web App shows Session Expired, "You have been signed out due to inactivity. Please sign in again to continue." and a Sign in link.
- Another form of Session Expired reads "Your session has expired due to inactivity. Click OK to continue from where you left off." Its OK button reloads the page.
When automatic termination of idle sessions is turned on, each Web App page of a concurrent account's session counts down the idle limit and restarts the count on every click or key press. At zero, the page checks whether the session's last activity is that old; if it is, or if the check fails, the Web App shows an Information panel with "You will be signed out due to inactivity in:", a count of Seconds from 30, and the Stay Signed In button, which returns to the previous page. Activity on another page of the same session also returns to it. When the count ends, the session is signed out, and the Web App shows Information, "Your session has expired due to an extended period of inactivity." and a Sign in link. Pages of a named account's session run no countdown.
Remembered sign-ins in the browser
When a user signs in to the Web App with the remember-me option selected, the login and the encrypted password are stored in browser cookies for ten days, and the next visit signs in from them. Without that option, the sign-in may still store the pair in temporary cookies for ten minutes; this is how a sign-in blocked by activation resumes. On a shared computer, the ten-day cookies hold a recoverable credential. Clearing the browser's cookies is a remedy for a sign-in that keeps looping.
In the Admin Center
User Sessions is one of the four pages of the Users & Security section, next to Accounts and Roles, Password Policy, and SSO Providers. One permission controls access to the section; see Permissions Reference.
The page has four panels: License Usage, the sessions chart, Logged Users, and Settings. The license figures, the list, and the chart load when the page opens. They reload only when you click Refresh or terminate sessions; the chart also reloads when you change its period.
Read the license usage
The License Usage panel has a Named Users row and a Concurrent Users row with these columns:
| Column | Named Users | Concurrent Users |
|---|---|---|
| Licensed | The license's named count. | The license's concurrent count. |
| Used | The number of different named accounts that have a live session. | The number of live concurrent sessions, counted in one application per account as described in Seat use. |
| Available | Licensed minus Used, never below zero. | Licensed minus Used, never below zero. |
| Accounts | The number of active accounts with the named license type. | The number of active accounts with the concurrent license type. |
| Connected | The same as Used. | The same as Used. |
Every cell shows a number or Unlimited. An unlimited license type shows Unlimited under Licensed and Available.
The sessions chart shows usage over time. Choose the Period (Today, Last 7 days, or Last 30 days), the License type (All, Named, or Concurrent), and a line, bar, or area chart. For a license type with a limited count, the chart draws the licensed maximum as a line.
View the active sessions
The Logged Users panel lists the active sessions, latest activity first, with the columns Login, User Full Name, User IP, Module, Session Type, Logon Time, Last Activity, and Duration.
Terminate sessions
- In the Logged Users panel, select one or more sessions. You can select several rows.
- Click Terminate. The button is enabled once a row is selected.
- In the "Are you sure you want to terminate the selected session?" prompt, click Yes.
Every selected session is terminated, with the moment of termination as its logout time; the selection is cleared, and the page reloads. A terminated session no longer takes a concurrent seat. In the Web App, the user sees the termination message the next time the Web App checks the session.
Terminate idle sessions automatically
Idle sessions of concurrent accounts can be terminated automatically. The setting is off by default, with a limit of 30 minutes.
- In the Settings panel, select Automatically terminate idle sessions for concurrent users after.
- In the minute(s) field, enter the idle limit. The field is enabled only while the check box is selected.
- Save the change with the save action that appears once either value has changed.
Clearing the check box turns the Web App's idle countdown off.
Review the User Sessions log
The Admin Center's User Sessions log lists each logged session with the columns Logon Time, User Full Name, Login, Session Type, User IP, Module Name, Last Activity, Logout Time, and the duration. Logout Time is blank while the session is open. The log is governed by the Admin Center's permission for logs, not by the permission of the Users & Security section. Deleting rows from the log needs, in addition, the permission to manage logs. For the other logs, see Logs.
To see one session's details, click its Logon Time. The User Session Log Record shows, in addition, Termination Reason:, Concurrent Session Count:, Named Session Count:, and Session Count: at that moment.
In the Settings App
The User Sessions node is in the Users & Security group. It shows a License Usage panel and the sessions chart above the Logged Users group, which lists the active sessions in a grid read from the same session data as the Admin Center's list.
Read the license usage
The License Usage panel has a Named Users: row and a Concurrent Users: row with the columns Licensed, Used, Available, Accounts, and Connected. The panel is refilled every time the list of sessions finishes loading, with the license read again first.
| Column | Named Users: | Concurrent Users: |
|---|---|---|
| Licensed | The license's named count, or Unlimited. | The license's concurrent count, or Unlimited. |
| Used | The number of active named technician accounts. | The number of live concurrent sessions, counted in one application per account as described in Seat use. |
| Available | Licensed minus Used, or Unlimited. | Licensed minus Used. |
| Accounts | The same as Used. | The number of active concurrent technician accounts. |
| Connected | The number of live named sessions, counted in one application per account in the same way. | The same as Used. |
Available is a plain subtraction, so a database with more active named accounts than the license allows shows a negative number. When the license has no seats of one type, that row shows N/A under Licensed and leaves the other four cells blank.
View the active sessions
The Logged Users grid lists the sessions that have not ended and have responded within the last five minutes. The reserved support account is never listed. Until you save a view of your own, the grid shows the columns Login, User IP, User Full Name, Module Name, Last Activity, Logon Time, and Duration. Duration is the time since logon in minutes, shown as < 1 min below one minute.
While the page is shown, the list is checked for changes every ten seconds by default. Refresh on the Logged Users toolbar reads the license figures and the idle-session setting again, reloads the list with its seat counts, and redraws the chart.
Terminate sessions
- In the Logged Users grid, select the session or sessions to end.
- Click Terminate on the Logged Users toolbar, or right-click a selected row and choose Terminate. The command is available while a row is focused.
- In the "Are you sure you want to terminate the selected session?" prompt, or "Are you sure you want to terminate n selected sessions?" for several rows, click Yes.
Every selected session is terminated, with the server time as its logout time, and the list is refreshed. A terminated session no longer takes a concurrent seat.
Terminate idle sessions automatically
Idle sessions of concurrent accounts can be terminated automatically. The setting is below the Logged Users grid; it is not shown when the license has no concurrent seats.
- In the navigation tree, select Users & Security > User Sessions.
- Below the Logged Users grid, turn on Automatically terminate idle sessions for concurrent users after.
- In the minute(s) box, enter the idle limit.
- Click Apply.
The idle limit applies to concurrent accounts only; a named technician's session does not time out on inactivity.
Review the User Sessions log
The log of sessions is under Logs > User Sessions. You cannot add, copy, or edit its records. It comes with six shared views:
| View | What it shows |
|---|---|
| List | All logged sessions. |
| Today | Sessions that started today. |
| This Week | Sessions that started this week. |
| by Module Name | Sessions grouped by application. |
| by User Full Name | Sessions grouped by user, with the termination reason as a column. |
| by Termination Reason | Sessions grouped by termination reason. |
Each view is sorted by logon time and shows the logon time, the user's full name, the login, the session type, the user's IP address, the application, the last activity, the logout time, and the duration, except the column it groups by.
A session's termination reason is one of these:
| Termination reason | Meaning |
|---|---|
| Logout | The user signed out. |
| Timeout | The session reached the idle limit. |
| Disconnect | The session was disconnected, stopped responding, or ended with no recorded reason. |
| Terminated | An administrator terminated the session, or a new sign-in of the same account replaced it. |
A log row gets its termination reason, its logout time, and the seat counts of that moment when the session's record is removed from the active sessions; until then it has no termination reason. When the session has no recorded logout time, the log uses a time at most five minutes after its last response.
Related topics
- License Management - the license and its named and concurrent seats.
- Logs - the product's logs.