In the very rare event that the Trusona service is not available, below are the noted mechanisms that can be used to bypass Trusona by select authorized users. Note that this must be configured in each system noted below and is not a substitute for the Trusona service or a method to circumvent the Trusona implementation.


Okta

https://help.okta.com/oie/en-us/Content/Topics/identity-engine/authenticators/configure-sspr.htm?cshid=ext-config-sspr


Keeper

https://docs.keeper.io/user-guides/troubleshooting/reset-your-master-password


MacOS

https://www.macworld.com/article/352153/how-to-unlock-your-mac-with-recovery-key-filevault.html


Windows

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-users-restore


Google Workspace

https://support.google.com/a/answer/33561?product_name=UnuFlow&hl=en&visit_id=638138291500629944-3605626405&rd=1&src=supportwidget0&hl=en#:~:text=Go%20to%20https%3A%2F%2Faccounts,in%20to%20your%20administrator%20account.&text=Try%20another%20way.,instructions%20to%20reset%20your%20password.

https://support.google.com/a/answer/3033063?hl=en&ref_topic=4388358


Zoom

https://support.zoom.us/hc/en-us/articles/10099872545037-Recovering-a-disabled-inactive-or-locked-account


SalesForce

https://help.salesforce.com/s/articleView?id=000385073&type=1


WordPress

https://wordpress.com/support/account-recovery/


Mac Recovery

This section covers what you can do if your system software is damaged such that you are unable to login or startup. You basically have 3 options:


1. Force macOS to Rebuild the Authorization Database

If your Mac fails to startup or allow you to login because it is unable to authenticate, you can disable Trusona by forcing macOS to rebuild the authorization database.

For this technique you will use the command line to remove the auth.db database files that reside in /var/db/ on the Mac’s boot drive. At next reboot, the OS will detect that /var/db/auth.db does not exist and create a new /var/db/auth.db, using /System/Library/Security/authorization.plist as a template.

sudo rm /var/db/auth.db

In macOS Recovery mode the "auth.db" file may be inaccessible. You can use the technique below to unlock and mount it.


Use Terminal from Recovery mode


The exact terminal commands may vary somewhat based on your startup drive configuration. The default startup drive is named "Macintosh HD" so we will use that in the description below.

Helpful UNIX commands:

ls list the contents of the current working directory.
pwd show the file path of the current working directory.
cd <directory-path> change the current working directory. 

rm remove the named file or directory.

You can search on-line for more detailed descriptions and options.

The basic strategy is to navigate to "/Volumes/Macintosh HD/var/db" and then remove "auth.db". When a file path name contains a space, you can enclose the path in quotes or use backslash '\' preceeding each space. In the steps below '#' is used to represent the UNIX command line prompt. The text that immediately follows is the UNIX command you should type.

Step by step guide

  1. Restart your computer in Recovery mode. On Intel press and hold Cmd-R as your computer restarts. On Apple Silicon Macs (ASM) press and hold the power key as your computer restarts until you see "More startup options".

  2. If FileVault is enabled, you will need a password to unlock the corresponding boot volume.

  3. From Recovery mode select Utilities > Terminal from the top menu bar.

  4. List the drives and volumes available

    # diskutil list

  5. Scroll through the listing to find the physical name of your startup volume. The volume may have a read-

    only section and read-write section identified with a "- Data" suffix.

  6. In this example "Macintosh HD - Data" is shown as "disk3s1". Your system will likely vary.

  7. Unlock the volume. You may be prompted for your FileVault password.

    # diskutil apfs unlock disk3s1
    After unlocking you should see a confirmation message: "Unlocked and mounted APFS Volume"; or Volume already unlocked.

  8. # cd "/Volumes/Macintosh HD" # pwd

    # ls

    Confirm you have found the correct boot volume as expected.

  9. # cd var/db

  10. #rmauth.db

  11. Restart your computer.

    # shutdown -r now

  12. Your computer should startup normally and allow you to login based on Apple's default configuration.


Remote login via SSH

  1. If Remote Login is enabled in System Preferences > Sharing a system administrator can login to your computer via SSH to uninstall Trusona.

  2. At a terminal window type: sudo rm /var/db/auth.db

  3. Restart your computer.


Unpair your mobile phone from your Mac

  1. Follow steps 1-8 above for using Terminal from Recovery mode.

  2. Navigate to Library/Application Support/Trusona

    You might need to prefix this with /Volumes/<boot-volume> from the root of your internal drive.

  3. List the contents of this directory with ls

  4. # cd <USERNAME>

  5. Remove the file named userCredential.trusona

  6. Restart your computer.

  7. Trusona authentication will require your password but will skip Trusonafication since your smartphone is

    no longer registered with your Mac.


Startup from another drive volume or partition

  1. Startup from a bootable backup if available. To startup from an external drive, you may need to use the Startup Security Utility in Recovery. If no bootable volume is available, from Recovery select Disk Utility to create a new APFS volume (Disk Utility -> Add APFS Volume). On older file systems you can create a new drive partition.

  2. Install macOS on the new volume you created above.

  3. During macOS install you will be asked to setup an administrator account with a username and password.

  4. After macOS installation completes, login to your freshly installed system.

  5. From here you can remove the damaged authorization database.

  6. Referencing the drive volume that is unable to startup you can use the following UNIX commands:

    # cd /Volumes/<VOLUME_NAME>/var/db

    # sudo rm auth.db

  7. Alternatively you can access or copy over files on your previous drive partition to rebuild a working system.



2. Restore from a backup if available.

To restore from a Time Machine backup you'll first need to re-install macOS and then use the Migration Assistant to transfer data from your Time Machine backup.

https://derflounder.wordpress.com/2021/08/04/downloading-and-installing-macos-big-sur-via-macos-recoverys -terminal/#more-11415


3. Salvage critical data and rebuild a working system.


We hope you never need these extreme techniques. We have documented them to reassure administrators they can work around even the most difficult problems.


See operating system instructions here: https://apple.stackexchange.com/questions/274032/backup-to-external-in-recovery-mode-terminal-or-time-machine