If NearAuth is unavailable
If NearAuth can't be reached, people who sign in through it can't sign in. This page lists how to switch your company back to signing in without NearAuth, and what to set up now so you can. Each switch is undone the same way once NearAuth is back. Print this page or save it somewhere you can reach without NearAuth: you won't be able to open it during an outage.
Is it NearAuth?
  • Status page: https://status.nearauth.ai
  • Health check: https://secure.nearauth.ai/health answers ok when NearAuth is working. You can point your own uptime monitor at it.
  • Call 607-238-3533 or email help@NearAuth.ai.
  • If only one person can't sign in, it's probably their phone (Bluetooth off, app removed, new phone). Don't switch the whole company: use the steps for one person below.

Prepare now
  1. Two break-glass admin accounts that never sign in through NearAuth, with long passwords and a hardware security key or authenticator app, kept somewhere safe. In Google Workspace, use super admin accounts (Google never sends super admins to a third-party sign-in). In Entra ID, exclude them from every Conditional Access policy that asks for NearAuth.
  2. Know who can make the switch: someone who can sign in with a break-glass account and has this page.
  3. Linux servers: keep one admin account that isn't in --users, or your cloud provider's serial console, and keep a copy of the uninstaller on each server:
    sudo curl -fo /root/uninstall-nearauth.sh https://secure.nearauth.ai/linux/uninstall-nearauth.sh
  4. Make sure people can sign in without NearAuth: people who have only ever signed in through NearAuth may not know their Google or Microsoft password. Be ready to send them a password reset.
  5. Practice once: switch a test group over and back, and time it.

Google Workspace
Sign in to admin.google.com with a super admin account and go to Security > Authentication > SSO with third party IdP > Manage SSO profile assignments.
  • Everyone: find the group or organizational unit assigned to NearAuth and change its assignment to None. People then sign in with their Google password (and Google's own 2-Step Verification, if it's on). It can take a few minutes to apply.
  • One person: remove them from that group.
  • When NearAuth is back: assign the NearAuth SSO profile to the group again.

Microsoft Entra ID
Sign in to entra.microsoft.com with a break-glass account.
  • Everyone: in Entra ID > Conditional Access > Policies, set the policy that requires NearAuth to Off. People then sign in with their password and any other MFA method you allow.
  • One person: remove them from your NearAuth group in Entra.
  • When NearAuth is back: turn the policy back On.
Don't delete the NearAuth external method: turning off the policy is enough, and is quicker to undo.

Apps that sign in through NearAuth
Apps you registered on the Service Providers page (Slack and so on) send people to NearAuth to sign in. For each app you need during an outage, sign in to the app's admin console with an owner account that uses the app's own password, and either turn off required single sign-on for now or point its single sign-on back at Google or Microsoft. Write down, now, which apps those are and which account can change them.

SSH to Linux servers
  • Open sessions keep running: the session watcher doesn't end sessions when NearAuth can't be reached (unless you set FAIL_CLOSED_MINUTES).
  • New logins need a certificate, which lasts 10 minutes. Log in with your admin account that isn't in --users (or the serial console) and run:
    sudo bash /root/uninstall-nearauth.sh --skip-deregister --unlock-passwords
    It gives locked-down users their old keys and passwords back without contacting NearAuth. When NearAuth is back, run the install command from the Linux SSH setup guide again.
  • Users who weren't locked down can still log in the way they did before NearAuth.

One person's phone is lost, broken or replaced
On the Users page, reset their devices so they can set up the new phone. Before you do, confirm it's really them (a call from a known number or in person), not just an email: someone pretending to have lost a phone is a common way in.