When the Mac is upgraded to 12.3 the Jamf connect gets stuck at DUO MFA login screen post AAD login at login window
Rolling back to 12.2.1 and it works fine
Any compatibility issue with 12.3 and Jamf Connect 2.10?
screenshot of post AAD login
In our environment, VMware Carbon Cloud also broke. We noticed a few deprecations including python 2.7 which might had been important for these applications to work.
We have the same Problem, but we have it directly in Prestage, we got the Window to logIN with our AD Accounts and then we receive an blank Window, does someone have a workaround ?
We have the Problem since 1 Month, but only with new Members, if they get onboarded, i tried with my Credentials and it works...its really wired
haven't been able to find a workaround/solution yet. I have a case logged with jamf support.
I did notice SecurityAgentHelper-arm64 process crash report logged in console same time when jamf login attempt is made at login screen
it could be something with com.apple.secureagenthelper.arm64 in 12.3 causing this
All of our vendors (DUO, jamf, VMWare), are pointing the finger at pointing the finger at Apple. There doesn't seem to be much movement from Apple on a supposed 12.3.1 to fix these issues (no betas available). I suspect that with the announcement of their "Business Essentials" service announcement, they won't move quickly.
12.3.1 is out. Not seeing anything encouraging about this particular issue here:
Just updated to 12.4, not knowing it was an issue and our NoMAD login is now gone. NoMAD is still there, but the branded login we had is no longer coming up and Shutdown, Restart and Sleep are now showing a the regular Mac login instead. Sleep we do have normally either.