HI Eskimo, I have filed a bug on Aug 18th, as there is no update on the bug, I have posted this in the forums. Here is the bug : FB13000811 (Lock Screen with SFAutorizationPluginView(old UI) is not hiding the macOS desktop). I have seen this issue on 14.0 beta 5 onwards, not sure of the earlier betas as I have not tried on them. Thanks & Regards, Tata Chaitanya

Hi Eskimo, Yes we are building authorization plugin and sure we will try to keep track of betas to verify our plugin. But this issue is being observed without our plugin in place. This should be reproduced with QAuthPlugins in place for screensaver. What I have followed is below: On macOS Sonoma, Updated the system.login.screensaver to use “authenticate-session-owner-or-admin” We get the lock screen as below. Even after locking the machine you can see the Desktop in the background. (I have kept screensaver info in terminal and OS details open on desktop and performed Lock Screen).

Hi Eskimo, I have updated the bug **FB13000811 **(Lock Screen with SFAutorizationPluginView(old UI) is not hiding the macOS desktop). As this issue is observed even without our product, Do you still want me to create a TSI request for this to check for a fix/solution? Sonoma preview is going to be available from 26th September, so do you think this will be addressed before that or how will we take this up? Thanks & Regards, Tata Chaitanya

Hi Eskimo, Do we have any steps/script to bring a custom/black background to hide the Desktop, so till the time we get a fix by Apple, we will use this as a work around. Do you suggest any alternate work around which will help us here? Thanks & Regards, Tata Chaitanya

Hi Quinn, As per the above conversation, I get Apple is working on a fix for this issue, is there any place where I can track the status as the bug I raised is still in Open state, and can we get informed here if a fix makes it to release? Is there any expected date? Thanks & Regards, Tata Chaitanya

Thankyou Quinn, Below is the bug details created for this. FB13550696 (Screensaver is not coming when system.login.screensaver is updated to use authenticate-session-owner-or-admin) Thanks & Regards, Tata Chaitanya

Hi Quinn, Can you please share me the latest QAuthPlugins. The one I have is couple of years old and the Readme documents in it do not have info related to FB13128730. Thanks & Regards, Tata Chaitanya

Hi Eskimo, I have replied on the original DTS mail communication, can you please provide the required info on the mail thread. Here is the Case ID received, Case-ID: 10703131 Thanks & Regards, Tata Chaitanya

It means that we have to pair the user with smartcard and macOS will takecare of unlocking the logon keychain with smartcard. However there are no public APIs to unlock the logon keychain with a smartcard. Is my understanding correct?

The peripheral manager only supports two advertisement keys: CBAdvertisementDataLocalNameKey and CBAdvertisementDataServiceUUIDsKey. Is there any way to send 16-byte custom data other than using CBAdvertisementDataLocalNameKey?

Hi Argun / @Engineer The peripheral manager is only supporting two advertisement keys: CBAdvertisementDataLocalNameKey and CBAdvertisementDataServiceUUIDsKey. Is there any way to send 16-byte custom data other than using CBAdvertisementDataLocalNameKey? Any pointers or example references on this will be helpful. Thanks & Regards, Tata Chaitanya

Thank you Quinn, Here is the bug number FB19544589 (Keychain is not getting opened after unlock when system.login.screensaver is updated to use authenticate-session-owner-or-admin)

Here is the FB number I have created FB19835797 ( On macOS Tahoe Icons in the prompts coming from macOS are getting left aligned)