The same as other Jamf Connect iDP deployments, yet different.
I know, it’s only a few days since I discussed deploying Jamf Connect Login with OneLogin, but as many people are using Jamf Connect with different iDP’s, let’s quickly have a look at another one: Google Cloud Identity.
Before taking it out for a spin, have a look at the admin guide here. As with all other iDP’s and Jamf Connect, the idea is to create an app in Google Cloud, and configure Jamf Connect via a config profile or custom settings plist.
However, Google is a bit different compared to other iDP’s and there are a few things I’d like to highlight before we have a look at the deployment.
Continue reading “Jamf Connect Login and Google Cloud Identity”
Another iDP tested with Jamf Connect Login
NOTE: I was told that configuring Jamf Connect with a OneLogin instance hosted in the EU does not work. See comments from Martin below. I presume this is an issue with the End Point Jamf Connect uses. Setting the OIDCProvider to "OneLoginEurope" does not work either.
Solution: set OIDCProvider to "Custom" and add the "OIDCDiscoveryURL" which you'll find here: https://developers.onelogin.com/openid-connect/api/provider-config
Hi all, it has been a while since I posted another topic. Things got a bit busy, and I’ve been struggling fixing things with both ADFS and Okta in Jamf Connect. I still have some remaining roadblocks to tackle on those and will try to update those issues I mentioned in my 2 previous posts ASAP. But in the meantime, let’s have a look at another iDP integration in Jamf Connect: OneLogin.
Trying this one out was actually a relatively smooth ride, although I’m facing one minor issue which I’ll discuss at the end of this post.
So Jamf Connect and OneLogin, let’s have a look.
Continue reading “Jamf Connect Login and OneLogin (and Secure Tokens”
And oh yes… I’m adding something about Secure Tokens as well..