We are building an authentication solution where we are building our own virtual smart card and perform certificate based authentication. We do not want to prompt the User for the PIN of the smart card and autosubmit the PIN on behalf of User through our authorization plugin. To achieve this we are removing loginwindow:login and passing th PIN to the underlying mechanisms by setting th PIN as part of KEnvironmentPassword attribute.With this change, we are observing that builtin:authenticate,privileged is invoking the authorization service instead of authorization_ctk service. Can you please let us know how do we autosubmit the smart card PIN in our authorization mechanism so that built:authenticate,privileged is invoking authorization_ctk service and perform certificate based authentication?

I am implementing an authorization plugin to provide support for an additional authentication method after Password for Mojave. I created a custom window subclassing NSWindow to show my UI. This UI is displaying properly at console login. But for screensaver unlock, the window is not visible on the black screen but it is having keyboard and mouse focus. I am using authenticate-session-owner rule for screensaver and adding my mechanism to authenticate right.I wanted help on how to bring this window to front and get it displayed on top of the screen saver.