We have a macOS application that adds entries to the Authorization Database (system.login.console) as part of its setup. We observed that after upgrading from macOS Tahoe to the macOS Golden Gate beta, the entries added by our application were removed, and the default system.login.console configuration was restored.
Is this expected behavior in the current Golden Gate beta, or is it a known issue? If it is a known issue, is there an expectation that it will be addressed in a future beta release?
Additionally, is there any recommended approach for preserving or restoring application-specific Authorization Database entries across major macOS upgrades?
It would be of great help if there is any suggested approach for the same.
We observed that after upgrading from macOS Tahoe to the macOS Golden Gate beta, the entries added by our application were removed
This doesn’t surprise me. My understanding is that this isn’t new behaviour. For a while now, major OS releases have reset the authorisation database. So, you’ll see the same behaviour if you update from macOS 15 to macOS 26.
is there any recommended approach for preserving or restoring application-specific Authorization Database entries across major macOS upgrades?
Not really. The best approach is gonna vary based on the target market for your product. For example:
- If you’re targeting enterprise environments, which usually have strict control over the OS update process, you’d create documentation for site managers discussing this issue.
- If you’re targeting normal Mac users, it would make sense to implement some sort of self-repair mechanism. But the exact approach you use for that is gonna depend on how your product is structured.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"