--- title: "Bypass Privacy Shield" slug: "xa-client-km-bypass-privacy-shield" description: "Break The Glass - Bypassing Privacy Shield The following registry settings would be implemented at installation by configuring the following registry keys." tags: ["4.11", "Settings", "Badge", "Client", "Support", "4.12", "Troubleshooting", "Fail", "How-To", "Registry", "Change Default Setting", "Timeout", "Endpoint", "4.14.0", "4.13.2", "Login", "Applications", "Getting Started", "Administration", "eXactAccess", "Install", "Installation"] updated: 2023-04-18T00:24:14Z published: 2023-04-18T00:24:14Z canonical: "healthcare.rapididentity.com/xa-client-km-bypass-privacy-shield" --- > ## Documentation Index > Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt > Use this file to discover all available pages before exploring further. # Bypass Privacy Shield with feature "Break the Glass" ![Broken Glass 2.png](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/Broken%20Glass%202%282%29.png) ## This feature is available in versions 4.10 and up (failover or logging in if Privacy Shield not working) HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\eXactACCESS] "SDAuthEnabled"=dword: 00000001 "LAORAuthEnabled"=dword: 00000001 ### The following are possible setting combinations that could be implemented using the above registry keys: SDAuthEnabled = 0 #### No failover provided. If the server is down, the user is unable to authenticate and may not bypass the privacy shield (Default behavior) SDAuthEnabled = 1 LAORAuthEnabled = 1 #### After a server-down scenario is detected, XA attempts to authenticate "locally" by performing a local login. This can use Windows-cached credentials. If Local login fails, the user cannot authenticate and may not bypass the privacy shield. SDAuthEnabled = 1 LAORAuthEnabled = 0 - After a server-down scenario is detected, XA attempts to authenticate "locally" by attempting to verify the user's password if they are already logged into XA. - If the user fails to provide the same password as the current user, the login fails, and the user is unable to authenticate and may not bypass the privacy shield. - If there are new credentials provided for a different user or no user is currently logged into the XA session, the new user may provide any credentials to unlock the current session, bypassing the privacy shield.