{"id":5832,"date":"2025-12-11T09:51:26","date_gmt":"2025-12-11T08:51:26","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=5832"},"modified":"2025-12-11T09:51:27","modified_gmt":"2025-12-11T08:51:27","slug":"authentication-reconnections-prerequisites","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/authentication-reconnections-prerequisites\/","title":{"rendered":"Authentication \/ reconnections \/ prerequisites"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

[Reading time: 2 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

This article explains how user authentication works in INO cx, the different reconnection and disconnection scenarios, and the prerequisites required to ensure a stable connection.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

1. Authentication<\/h2>\n\n\n\n
\"\"<\/figure>\n\n\n\n

1.1. Login<\/h3>\n\n\n\n

To sign in to INO cx, users must have an active account with a username and password. When a new account is created, the user receives an email to set up their password and confirm their account.<\/p>\n\n\n\n

If the user has not confirmed their account, an activation link can be resent. This action requires the modification of users permission in the Maker (role).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

1.2. Password expiration<\/h3>\n\n\n\n

In the Maker, within the customer account settings, administrators can enable Password expiry and configure a password expiry timeout between 30 and 365 days.
If enabled, users will be required to create a new password once the configured duration has been reached.<\/p>\n\n\n\n

1.3. Invalid password<\/h3>\n\n\n\n

Users may attempt to sign in up to 10 times. After 10 invalid attempts, the password must be reset.<\/p>\n\n\n\n

The user can click Forgot password to receive an email with a reset link.<\/p>\n\n\n\n

Another user with the appropriate rights can also send the reset link manually from the Maker:
Maker > Users > Gear icon next to the user > Reset the password for v4
The reset link is valid for 2 hours.<\/p>\n\n\n\n

1.4. User already connected<\/h3>\n\n\n\n

A user who is already signed in cannot log in again from another computer or from another session on the same computer at the same time.<\/p>\n\n\n\n

1.5. End of trial period<\/h3>\n\n\n\n

If the customer account has reached the end of its trial period, users will not be able to sign in.<\/p>\n\n\n\n

2. Disconnections<\/h2>\n\n\n\n

If the user signs out from one browser tab, all open tabs will be logged out simultaneously.<\/p>\n\n\n\n

A supervisor can disconnect a user directly from the Banner in the Supervision module.<\/p>\n\n\n\n

If the network connection is unstable, the Banner will attempt to reconnect for up to 30 seconds. If reconnection fails, the user is logged out.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n

In the Maker, a small indicator (green, orange, or red) displays the current connection status.<\/p>\n\n\n

\"\"<\/figure>\n\n\n\n

3. Prerequisites<\/h2>\n\n\n\n

A direct link on the login page (at the bottom) allows users to Check my configuration<\/strong>, which runs several diagnostic tests grouped in four sections.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

3.1. Browser<\/h3>\n\n\n\n

Checks cookies, pop-ups, screen resolution, local storage availability, and more.<\/p>\n\n\n\n

3.2. Sockets<\/h3>\n\n\n\n

Displays the connection status with the connected date and time.<\/p>\n\n\n\n

3.3. STUN<\/h3>\n\n\n\n

Runs STUN connectivity tests.<\/p>\n\n\n\n

3.4. System<\/h3>\n\n\n\n

Shows CPU core count, estimated network latency, available memory (GB), and other system metrics.<\/p>\n\n\n\n

Users can download the diagnostic report, which includes WebSocket logs and statuses.
A Re-check option is also available.<\/p>\n\n\n\n

\u26a0\ufe0f Please ensure that all prerequisites are met. The detailed list is available here<\/strong>: Chrome and WebRTC prerequisites<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

[Reading time: 2 minutes] Overview This article explains how user authentication works in INO cx, the different reconnection and disconnection scenarios, and the prerequisites required to ensure a stable connection. 1. Authentication 1.1. Login To sign in to INO cx, users must have an active account with a username and…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[103],"ht-kb-tag":[],"class_list":["post-5832","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-ino-get-started"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5832","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=5832"}],"version-history":[{"count":6,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5832\/revisions"}],"predecessor-version":[{"id":5844,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5832\/revisions\/5844"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=5832"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=5832"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=5832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}