I've been trying to get the trial version of Jamf Connect Login to work since Wednesday and can't seem to figure out what I'm doing wrong. I even tried following Traveling Tech Guy's blog post : https://travellingtechguy.eu/jamf-connect-login-with-azure/
But the results are the same.
Here's what's happening: Azure login window pops up asking for credentials. I put in my credentials. Next screen says create a new local password and verify with a greyed out Create Account button. Thing is - the moment I start typing the app goes black and starts over from the beginning.
Good advice, submitted a support ticket with Jamf support and have been working with them for the past two days. The team is very helpful and looking into it now. My main intention for reaching out to the community was to see if anyone else was experiencing this issue and how they resolved it.
My main concern is that I think this product could solve a lot of pain points for us and that I want to get this working before the trial ends. It certainly wouldn't be easy to convince my director to purchase this product if I can't get it running.
SCG - so you never get to the screen at the top of traveling tech guy's blog post then? Have you run the debugger? Do you know when you check your azure portal for the Enterprise App if it shows that the test user successfully accessed Azure?
$ ssh user@ip $ log stream --predicate 'subsystem == "com.jamf.connect"' --debug
Are you seeing any errors?
So update: Jamf support escalated two times to different team members but the results were the same. At the end of which my sales support rep recommended that I buy a license as the version I was using was a beta and that the issue was resolved with a subsequent update that had not come out yet.
I received the license and tried again. The issue persists. I'm really stumped here. Hope someone knows the answer.
Edit: Upgraded to Mojave from High Sierra and the issue resolved. Reached out to Support to let them know about this and received back a message explaining that they found a bug in the current roll out that was causing 10.12 and 10.13 to fail but it works on 10.14.