Screen Not Locking with authenticate-session-owner-or-admin in Screensaver

I modified the system.login.screensaver rule in the authorization database to use authenticate-session-owner-or-admin instead of use-login-window-ui to display a custom authentication plugin view when the screensaver starts or the screen locks.


However, I noticed an issue when the "Require Password after Display is Turned Off" setting is set to 5 minutes:


  1. If I close my Mac’s lid and reopen it within 5 minutes, my authentication plugin view is displayed as expected.
  2. However, the screen is not in a locked state—the desktop remains accessible, and the black background that typically appears behind the lock screen is missing.


This behavior differs from the default lock screen behavior, where the screen remains fully locked, and the desktop is hidden.


Has anyone encountered this issue before? Is there a way to ensure the screen properly locks when using authenticate-session-owner-or-admin in the screensaver rule?



Posted on Apr 1, 2025 4:08 AM

Reply
5 replies

Apr 2, 2025 3:37 AM in response to leroydouglas

I read an article online that mentioned changing the rule in system.login.screensaver within the authorizationdb. I followed the steps to modify the rule using a command and successfully changed it. However, I encountered an issue:


When I close the lid of my MacBook Pro, it goes into sleep mode. My lock screen setting is configured to require a password after a 5-minute delay once the display turns off. If I open my Mac within 5 minutes, the password prompt appears, but the black background does not show, and the desktop remains accessible.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Screen Not Locking with authenticate-session-owner-or-admin in Screensaver

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.