Concurrent users are frevvo users that are logged in simultaneously. frevvo displays a max user limit has been reached message for tenants with limited concurrent users licenses when more than the allowed number of users attempt to log into frevvo. This can also happen when users close their browsers without logging out, because these sessions count towards the user limit until the Session Timeout configured for the tenant has been reached (the default session timeout is 30 minutes.)
What does the Superuser/tenant admin(s) do if users are reporting this error?
The Manage Sessions link on the Manage Tenant page opens the User Interface to view/manage the number of active users. The UI is available to:
- The initial Tenant Admin user (set up when the tenant was created). The tenant admin login is the only user allowed to login when the maximum number of concurrent sessions has been reached. This login is not counted against the license. The tenant admin can view/manage active users only for their tenant.
- Superuser admin - view/manage active users for all tenants by navigating to each tenant and clicking on the Manage Sessions link
- Additional admin users - view/manage active users but this login will be counted against the license and listed in the Sessions Table. Additional admins will not be allowed to login once the max user count is reached.
On This Page:
View Active Users
The Manage Sessions Page displays the current number of sessions and the max session count based on your frevvo license. A table displaying the current active user sessions provides the following information:
- User Id
- Last Access Time
- Login Time
- Does the user have the frevvo.Designer role? (Yes/No)
- User's device - (Desktop/Tablet/Phone).
Session Timeout (min) - the session timeout in minutes set up for the tenant.
The 30 minute Session Timeout setting shown in the images is the default value for frevvo running in an on-premise environment. The value for tenants in the frevvo Cloud will change based on operational needs.
The entries in the table are sorted by last access time in descending order. Columns in the Sessions Table that are sortable display the up and down arrow icon in the column header. Clicking on the up section of the arrow icon in one column sorts all the columns in the table in the ascending direction. Clicking on the down section of the arrow icon in the column header in one column sorts all the columns in the table in the descending direction.
The table shows a maximum of 200 entries. Twenty-five sessions per page display but you can change that to 10, 50 or 100 by clicking the preferred option in the Show Entries dropdown.
Manage Active User Sessions
The tenant admin can take one of two actions to reduce the number of active users:
- Send an email to a selected user requesting they log out
- Kill a selected user session.
You can only select one user at a time.
When a session in the table is selected, the Kill Session and Request Log Out buttons are enabled.
Send Logout Request
Follow these steps to send a logout request to a user:
- Click the checkbox to select the user from the Sessions Table.
- Click the Send Logout Request button.
- Customizable Email Subject and Message fields display. Both fields are required.
- Click Send. An Email Has Been Sent message displays.
- The user will receive the Logout Request email.
When the notified user logs out, the Sessions Table will reflect the change.
- Click the Refresh button to manually update the Sessions table.
- The Session Timeout that displays in the table reflects the value entered on in the Session Timeout field when Editing the tenant. If the field is left blank, the default value of 30 minutes displays.
Cloud Server logs will show INFO level statements about the Log Out Request email.
Follow these steps to terminate a user session:
- Click the checkbox to select the user from the Sessions Table.
- Click the Kill Session button.
- Click Ok when prompted to confirm the action.
- The Session Has Been Killed message displays:
The Sessions table automatically refreshes with the updated information.Click the Refresh button to manually update the Sessions table.
- Users performing a workflow Task from their Task List or designers developing forms/flows when their session is killed, will see the error:
, When the Continue button is clicked, they will immediately be presented with the login screen. Changes to the Task or form/flow will not be saved. They will have to login again and establish a new session.
The user will receive an email explaining that their session was terminated by the administrator
Cloud Server logs will show INFO level statements reflecting who killed the session
Additional Admin Users
Users added to the tenant as additional administrators will be able to - view/manage active users but their login will be counted against the license and listed in the Sessions Table. Additional admins are not allowed to login once the max user count is reached. Admin users managing user sessions will be prevented from killing their own session if they attempt to do so. The message displayed is shown in the image:
The Superuser/Tenant Admin can kill sessions for additional admin users.
LDAP, SAML or Azure Security Managers
You may notice a slightly different behavior if your tenant is configured for the LDAP, SAML or Azure Security Manager. The tenant admin user setup when your tenant was created or a tenant admin user set up in your IDP will be able to login once the max user count is reached.
For example, a tenant configured for the SAML Security Manager has an initial tenant admin user set up when the tenant was created (backdoor admin) and has a tenant admin user in the Active Directory that SAML is using.
You can log into the tenant after the max user count is exceeded by:
- Browsing this URL - and logging into the tenant as the backdoor admin OR
- Browsing this URL - and logging in as the SAML user tenant admin .
The tenant admin user will not appear in the Manage User session list or be counted against the license.
Logging in as a user from the Manage User screen
Once the max user limit has been reached message displays, the superuser/tenant admin cannot login as a user from the Manage Users page.
The tenant admin will see this message:
Changes to the Server Configuration screens
The Server Configuration screen, accessible to the superuser admin, shows the following changes:
- Max Concurrent Users has been renamed to Max Concurrent Sessions.
- The Current Session Count across all tenants has been added to the table.
The Tenant Admin will still see Max Concurrent Users on the View Configuration screen.
Cloud Log Entries for User Sessions
As users login/logout of frevvo, entries in the frevvo Cloud logs are captured. Here is a snippet of the logged statements when users jessica, robert and the tenant admin login and then logout of a tenant named mycompany.