I have raised an enhancement request as suggested, please do find the reference here https://feedbackassistant.apple.com/feedback/24412830 . As this worked upto Tahoe, can you kindly help us to understand if this is an intentional change made to SFAuthorizationPluginView in macOS 27 Beta?

I have raised a bug for the same. Please do find the reference for it https://feedbackassistant.apple.com/feedback/24396407. Can you kindly attach it to oleksandr91 bug so that we can get regular updates too. Also, we have updated and tried in macOS 27 Beta 6 , but noticed that the issue is still reproducible.

We are trying to customise the macOS native SFAuthorizationPluginView as shared in the image below. These are the points that we are trying to achieve and the reference text and image is attached as below, We are trying to customise the lock icon into a customised logo. (Company logo with wifi icon) We are trying to customise the button text and color from "Ok" to "Submit" We have customised the text "You must enter a password to unlock your screen" to "OTP" We have customised the text "Enter your password to continue with "macOS"" to "Customised Text" All these were achievable upto macOS Tahoe and has been not possible since Golden Gate Beta 1 and the behaviour remains same on Beta 6 too. Can you please suggest us if there are any approaches available to achieve these customisations?

Thanks for the quick response. We observed that this behavior was present in the native macOS SFAuthorizationPluginView in Beta 1. However, in Beta 5, the issue appears to occur only when a third-party authorization plugin is used. We are not seeing the same behavior with the native macOS SFAuthorizationPluginView. Please find the attached screenshot showing the behavior with the native SFAuthorizationPluginView. Could you please clarify why there is a difference in behavior between the native macOS SFAuthorizationPluginView and the same view when a third-party authorization plugin is integrated? Our third-party plugins have not made any changes to, or taken any action on, the buttons displayed within the SFAuthorizationPluginView. Is this a known change in Beta 5, or can we expect this behavior to be addressed in one of the upcoming beta releases? Any clarification would be greatly appreciated.

We had tried similar upgrades from Sequoia to Tahoe and we havent noticed any issues with the authorisation db. It was retaining any custom entries added to it during OS upgrade. Is this change a recent one due to which third party applications will be impacted?

Yes , I meant the SFAuthorizationPluginView of MAC. We are trying to authenticate-session-owner-or-admin in system.login.screensaver authorisation db.

No this is a separate issue and not linked to the thread https://developer.apple.com/forums/thread/825491. This was observed during reboot of the machine when File Vault is enabled and not in SFAuthorization flow.This has been observed since macOS 13.x and we continue to see the same until macOS 26.4.1.

Thanks for sharing the existing thread details, is there any particular fix for making the window act as the first responder or any plan from Apple to fix it in upcoming releases?