"The endpoint only accepts POST requests. Received a GET request." in Jamf Connect 2.44.0

Had a report of the same thing. User has been around a while, although not as long as myself, and I don't have the same problem. macOS 15.3.1, Jamf Connect 2.44.

---

@dan_berlyoung wrote:

I have a 2019 iMac running Sequoia that uses the same Connect setup as 700 other systems that is showing this error message. It only seems to come up when logging onto the system using an ID that was created a long while ago. I tried using an account that hadn't been used on this system before and it works fine. And continues to work fine for that new ID.

Nothing has changed in our EntraID configuration and it is currently working fine for systems in that lab as well as all across campus.  Any ideas?

 

---

The issue appears to be related to specific user accounts, particularly older ones. Possible causes include corrupted user profiles, outdated EntraID cache, password policy conflicts, or Sequoia-specific issues. Troubleshooting steps involve creating new user accounts, repairing existing profiles, clearing the EntraID cache, reviewing password policies, and checking Sequoia logs.

I would reach out to my Identify Management Team and check for the Sign in logs to identify the issue for this particular users,

I tried creating a new account on that physical system and the new account worked just fine.  I then tried deleting the existing bad account and then signing on again to recreate it and that did not solve ie.

How would I go about clearing the EntraID cache? Is there something that will survive a local account being deleted?  Thanks!

Experiencing this same issue with conditional access policies and running jamf connect 2.44.  Have you had any luck figuring out a work around?  If I bypass the conditional access policy it appears to work, also as mentioned new users(those logging into the computer for the first time) do not seem to have this issue. 

Update: in my case it looks like a configured passkey was the cause.  I removed the passkey and have had repeated success logging in.

I also have an end user experiencing this issue as of today. They reported that they had previously set up a security key (hardware passkey), such as a YubiKey, within Microsoft Entra, and it was working with Jamf a few weeks ago. However, they are now encountering the same error mentioned above.

Notably, if they remove their YubiKey from their Entra 2FA setup, Jamf Connect works again.

• macOS Version: 14.6.1
• Jamf Connect Version: 2.44

Does Jamf Connect support the use of security keys like YubiKey?

I've been working with Jamf Support on my issue and it might be related to what everyone else is experiencing. Jamf Connect does not support hardware passkey such as Yubikey. This may extend out to other passkey settings. @tmagdziasz your solution is at this point the best route to go - remove the passkey from the authentication process.

I did revert back to Jamf Connect4 2.43 for this particular user and they were able to log back in with their authenticator app (not Yubikey).
https://learn.jamf.com/bundle/jamf-connect-documentation-current/page/Multifactor_Authentication.html