06-04-2024 03:05 AM - edited 06-04-2024 03:14 AM
Hi Folks,
It’s been a while since the last time I posted, and I have been tinkering with a few side projects. Hopefully I can bring more cool stuff to the community once these projects come to fruition. Today, I’m excited to introduce the first one:
What if you’re using Okta as your primary IdP but are also yearning for JumpCloud’s UEM features?
Imagine using Okta SCIM to provision users (and their passwords) to JumpCloud, then letting JumpCloud sync the same identity to the device while managing it simultaneously. Sounds intriguing, right?
Let’s dive in!
Now it’s all set, let’s dive into a few scenarios to see how it looks from a user perspective.
MacOS
Windows
In this particular setup, as mentioned above, user will manage their passwords in Okta only. You probably will consider hide the JumpCloud tray app (which empowers the user changing their JumpCloud passwords on-device) to avoid confusion.
Create and bind the policies below to device groups respectively.
Hide Windows App Using a Policy - JumpCloud.
Create a Mac JumpCloud App Controls Policy
On Windows, after the password change, user will need to login with the new password to re-engage Windows Hello (PIN or biometric):
On MacOS, user will need to input the previous password in order to regain access to keychain:
When you deactivate or delete a user in Okta, the user is placed in a suspended state in JumpCloud.
That’s it (for now)! Thanks for reading this far, hope these use cases are helpful, and feel free to comment below if you have any questions/feedback.
Catch you up on the next one!
New to the site? Take a look at these additional resources:
Ready to join us? You can register here.