Hey there! Quick question. I am testing NoMAD with quite a success. This is the initial test to then move to Jamf connect with Azure AD. Here is the first challenge I want to solve.
Nomad works great when it comes to password sync and keychain management. However, our users are used to change their passwords via "Security Settings" or Change password from User Preferences.
I noticed that if I change my local password locally and not with nomad, Nomad will still connect and the passwords are now out of sync.
I would like to enforce users somehow to change their passwords via nomad. Not sure if blocking the entire user and security preferences is the best strategy.
Any Ideas? how did you guys deal with this kind of situations? Changing the password locally creates a password miss-match with the AD password that will only resync if the user signs out and signs back in.
Alternatively, I was thinking if there is an extension attribute that I can use to check if NoMAD is synced.
Any help is highly appreciated.
