Having problems creating local user accounts using Jamf Connect, SSO credentials as part of Setup Assistant.
Actual Workflow Behavior
Any help, insight anyone can offer is greatly appreciated. I'm also happy to provide more clarification.
Hey wblack, thank you for your suggestion!!
Our troubleshooting was wayyy too in-the-weeds and missed that.
Edited our PreStage Enrollment to skip account creation. It's now closer to behaving as expected, but now Jamf Connect Login asks us to re-type our SSO password and continually refuses to accept it.
I have a feeling this is now something to do with FV2. We shall see! I have a support case open now.
It may be more about your SSO settings. In our environment, SSO kicks in first, before Jamf Connect, as our IdP is Azure.
Does the user being entered a part of the SSO group? It may depend on the IdP you are set for SSO. We had to make the users match in both the Jamf Connect and Jamf SSO Azure enterprise apps.
Keep testing, and keep testing, I can assure you of that.
Thank you again for your time and responses! I wanted to write a follow up in case it helps anyone else down the road.
Our PreStage Enrollment was configured to create an additional admin account. Despite receiving the aforementioned errors when trying to create/authentication with an MS365 account, we let the computer complete PreStage Enrollment and logged in locally using the admin account.
Once in, found mpjamf_login.log. It contained authentication attempts for both the MS365 account as well as the local admin account. For reference, I've attached a sanitized copy of the log that pertains only to the MS365 account.
Focusing on the log events pertaining to MS365, a couple errors appeared with each authentication attempt:
There were a few others not listed here.
Not sure where to begin, I picked the 3rd error, above, and Googled. I eventually found https://community.powerbi.com/t5/Developer/The-request-body-must-contain-the-following-parameter-client/td-p/259147, specifically the last post of the thread made by user "jayendran".
Following what their post suggested, we checked our Azure App Registration settings, and sure enough our "Default client type" setting was set to "No". Flipped it to "Yes", saved, and Jamf Connect Login with PreStage Enrollment worked!!!!
Jamf Connect Login now creates a new local user as advertised. I wrote a similar summary for our Jamf Support case so they can update their documentation to reflect Azure's new App Registration UI that jayendran pointed out.
I hope this helps anyone in the future.