There was no edit option, so I am adding mechanism array here in structured form <array> <string>builtin:prelogin</string> <string>builtin:policy-banner</string> <string>loginwindow:login</string> <string>builtin:login-begin</string> <string>builtin:reset-password,privileged</string> <string>loginwindow:FDESupport,privileged</string> <string>builtin:forward-login,privileged</string> <string>builtin:auto-login,privileged</string> <string>builtin:authenticate,privileged</string> <string>PKINITMechanism:auth,privileged</string> <string>builtin:login-success</string> <string>loginwindow:success</string> <string>HomeDirMechanism:login,privileged</string> <string>HomeDirMechanism:status</string> <string>MCXMechanism:login</string> <string>CryptoTokenKit:login</string> <string>loginwindow:done</string> </array>

Thank you so much for reply, I am exploring below option for smart card Persistent tokens are not tied to hardware. You can create one that’s fully virtual, for example, one that works over the network It will be very helpful if There will be any implementation guide or sample for this

Thanks @DTS Engineer Kevin Elliott for your reply My larger goal here is at the lock screen I want to detect what events occured to reach this lock screen, is it logout,lock,restart or shutdown? Is there any kernel level file or any other changes I can track from daemon to get to know this

So, I have one app which has build on Xcode 16, when using that app in tahoe OS , button is not showing background white color, it shows as borderless so same button behaves differently in different OS Note- App has build on xcode16(Sequoia) attached image of button from app from both OS this is from sequoia This is from Tahoe OS attached button's attribute inspector

This behaviour I observed in Intel based Mac device, In Apple silicon based its working fine

@DTS Engineer We are using an SFAuthorizationPluginView-based authentication plug-in for screen unlock. We are seeing a different issue on macOS Tahoe 26.4.1: during the lock/unlock flow, Apple’s default lock screen appears first, and after entering the password there, our plug-in lock screen appears afterward. In effect, the lock screen is shown twice. Based on your guidance in this thread, we tested setting screenUnlockMode = 2 in /Library/Preferences/com.apple.loginwindow, and that appears to resolve the issue. We would like clarification on the lifecycle and supportability of this setting: What supported values exist for screenUnlockMode, and what behavior does each value enable? Is this a supported public setting, or is it considered an internal compatibility workaround? Can this setting be managed through MDM, and if so, through which payload/key? On systems where this key is absent, is that equivalent to a specific default value? For uninstall/rollback, should we restore the original value if present and delete the key if it was previously absent?