-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After a macOS update/upgrade, Escrow Buddy is no longer in the authorization database. #22297
Comments
Thanks for sharing and thanks for the PR. We'll take a look at this today or tomorrow! |
OS update resets, |
QA Notes:
|
Hi @PezHub , Thank you for your reply.
|
With each Mac update, |
Fleet version: v4.55
💥 Actual behavior
After a macOS update/upgrade, Escrow Buddy is no longer in the authorization database.
🧑💻 Steps to reproduce
🕯️ More info
Some macOS updates and upgrades reset the authorization database to its default state, which will deactivate Escrow Buddy and prevent FileVault key generation upon next login.
Although this behavior adds friction to administering Escrow Buddy on your Macs, it's actually a great opportunity to test new macOS versions and ensure Escrow Buddy (or any authorization plugin) works as expected before reflexively re-enabling.
Once you've tested and are confident that Escrow Buddy works with the versions of macOS your company Macs are running, you can run this command (in root context) to re-enable Escrow Buddy in the authorization database:
/Library/Security/SecurityAgentPlugins/Escrow\ Buddy.bundle/Contents/Resources/AuthDBSetup.sh
Tips for configuring this on various MDMs can be found in the Examples wiki page.
Also see this related blog post: Managing login mechanisms in the macOS authorization database
The text was updated successfully, but these errors were encountered: