Hello,
I'm new to the Jamf community and have some questions about Jamf Connect and Verify in particular.
After some testing, we have identified some issues that will cause problems:
- Our identity provider is Azure, if a person changes his azure password, he loses the local synchronization and must enter his new password Azure, only he must also enter the old password of the local account, except if the person doesn't know his old password anymore (which is the case of most people who change their password with us). It can't finalize the synchronization with Jamf connect verify .
Is there a solution to this problem?
Second case, a little brutal, if we change the email address of the Azure account, necessarily Jamf Connect Login recreate an account because for him this new address does not correspond to the local account previously created.
It's possible that in case of a change of email, he keeps the same local account? (the Migrate option does not propose migration in this case ...)
Last point, about FileVault, indeed when Filevault is activated, it adds a connection layer (local MacOs identification page) and only then it launches the Jamf Connect connection mechanism, it's a very heavy procedure.
It's possible to override / disable the first local connection? ( caused by the option : DisableFDEAutoLogin )
Thank you.
