Post not yet marked as solved
We displayed a custom unlocking NSWindow over the screensaver. On El Capitan and Sierra it was working perfectly.Starting from High Sierra, it stopped working at all.The NSWindow simply never shows up. Setting the windows level to NSScreenSaverWindowLevel or higher has no effect.Is there any way to resolve that issue?
Post not yet marked as solved
Is there a correct way to customize the default Fast user switching UI. I tried the same approach as for the login window.I took the system.login.fus right and replaced the standard mechanism loginwindow:login to our own that we use for the login window, where it works very well. But for fast user switching, there're several issues:- The actual native fast user switching screen is not shown, instead? all I see is a popup saying "macOS wants to make changes..." with an unlock button.Also this popup may contains UI elements for the custom NSView of SFAuthorizationPluginView.- the dictionary inUserInformation is always null in the willActiveWithUser method of SFAuthorizationPluginView. So, it's impossible to get the username.
Post not yet marked as solved
Hello,I've installed the macOS Catalina beta 2 to test our custom authorization client (plugin), but I noticed that it doesn't work over a screensaver at all. Then I tried the default client but with the authenticate-session-owner-or-admin rule for the screensaver.If I modify the system.login.screensaver rule to use authenticate-session-owner-or-admin instead of use-login-window-ui, then I see no UI trying to unlock the running screensaver, no matter how many times I try.Is that a bug, or Apple broke authorization plugins for a purpose. I know that the authenticate-session-owner-or-admin rule uses the legacy code, and Apple is only interested in the modern 'fancy' use-login-window-ui. But only the first one supports plugins.For the last three years Apple is adding more and more bugs in that area from one release to another. I have a number of bugs that has been ignored by Apple for a year or two.So, my question is there any hope to have this issue fixed in the macOS 10.15 release?Because as for now, this totally brokes our product
Post not yet marked as solved
Hi,Is there a way to figure out from a code if a local user account is actually a mobile account on High Sierra?On Sierra I checked the kODAttributeTypeAuthenticationAuthority attribute of the user ODRecord.By on High Sierra I can't find this attribute anymore. Is there any other ways to check this ?
Post not yet marked as solved
We developed an authorization plugin with our custom UI. It worked perfectly on El Capitan and Sierra.But on High Sierra it stopped invoking when a user clicks the lock item in System.Preferences.To invoke our plugin, we changed the authenticate right in the authorization database. { 'class' : 'evaluate-mechanisms', 'mechanisms' : [ 'builtin:authenticate', 'builtin:reset-password,privileged', 'builtin:authenticate,privileged', 'PKINITMechanism:auth,privileged' ], 'shared' : 'true', 'tries' : '10000' }Actually, we replaced builtin:authenticate with a mechanism from our plugin. We found that the authenticate right is not invoked on High Sierra, when a user clicks any locks in System.preferences.Is that a bugs? Are there any other ways to invoke a custom UI mechanism for unlocking?
lex.andreev.