Auto relogin

auto relogin ( isautoreloginenabled ) this article documents the contact center server preference isautoreloginenabled , which controls whether the web client uses an enhanced keep alive and automatic re login path after prolonged connectivity loss it complements the agent facing steps in docid\ yrdli1lqghr n iz38vtn naming — the preference key in the server preference store is isautoreloginenabled the product ui may label this concept as “auto re login” or similar purpose when enabled , after the client detects sustained keep alive / ping failures (or a keep alive timeout), the application can navigate to an auto re login flow when connectivity returns, the client verifies that the same browser origin is reachable (rest /ameyorestapi/echo ) for supported agent class roles, re authenticates using credentials already held by the client (force login), then re syncs saved ui state (for example campaign, extension, agent status) so the user is not prompted to type user id and password again on the login screen when disabled , the client uses the standard keep alive timer only; recovery from outages is left to normal session behavior and manual login if the session is lost configuration item detail preference key isautoreloginenabled type boolean (store and interpret as string true / false where applicable) scope (code) read at contact center hierarchy via the server preference store ( contact center context and contact center id) who sets it typically an administrator (or operations) using your deployment’s server preference store tooling for the target contact center after change follow your standard process for applying server preference updates (for example reload server preference store where required — see ) same origin — recovery pings use the current page host ( location ) the feature does not switch the browser to a different hostname (for example a manual “failover url”) designs that rely on dns/vip or reverse proxy so the same url maps to a healthy node are compatible; designs that require the user to open a different host are not covered by this mechanism alone related client behavior (reference) the following are implementation details useful for support and advanced troubleshooting they are not separate administrator preferences in the codebase reviewed for this page behavior notes keep alive interval fixed client interval ( 20 seconds ) between keep alive attempts when auto re login mode is active keep alive timeout check separate 12 second repeating check can treat a stuck keep alive as overdue and trigger the auto re login path failures before auto re login consecutive keep alive failures beyond a configurable maximum (default 3 , meaning more than three failures) can trigger auto re login; the maximum can be supplied per user via getmaxpingfailurecountforuser (server) echo poll (recovery) after entering auto re login, the client polls /ameyorestapi/echo about every 3 seconds until http 200 is received, then proceeds with re login and state sync fast failures (for example browser offline in developer tools) may space attempts 20 seconds apart; a short outage may therefore recover without entering the auto re login screen if the next keep alive succeeds before thresholds are met roles and ux area behavior (summary) professional agent, executive after server is up again state sync path including force login with stored credentials; then return to the previous place where possible; optional webrtc re registration when applicable supervisor, analyst, administrator, user access manager after server is up save user data event / local storage path rather than the full agent sync chain (see client autoreloginpresenter implementation) exact role names in your deployment may follow your license and user type configuration product version notes release notes have referred to autoreloginphoneagent and similar flags in patch history; align operational runbooks with the actual key in the preference store for your version ( isautoreloginenabled for the path described here) validate behavior on your specific release before enabling in production (see for example contact center patch release notes 6 9 0 in this repository’s release notes) see also docid\ yrdli1lqghr n iz38vtn — end user login steps and campaign selection docid\ fbiw3gzuebtt1nuaxjsor — reloading server preference store after changes docid\ tl7a4uh s7hsxqpmiag44 — crm loginhandler behavior mentions auto re login in integration contexts