We have a few use cases for JumpCloud. One is SSL for some legacy applications, LDAP, user provisioning, MFA access into the AWS environments, and some third-party apps for monitoring. There are also things like Datadog and New Relic that can be added as use cases.
Another use case is for system access for our EC2 instances, you can SSH in those instances. It will install a Linux user ID and provide the public key that is assigned to that specific user.
I have also used it for some automated scripting, although there are a lot of tools in that space. JumpCloud has a lot of features. I use this tool to consider how this system is managed; if it uses our standard, and if it is a legacy system. I have used the JumpCloud agent to run scripts arbitrarily on systems to see if I will get back information.
Additional use cases include using it for audits, SOC 2 Type 2, and status scope for FedRAMP. I have used their API extensively to make web requests, get back JSON data, and turn that into Excel spreadsheets, etc. to show the auditors.
I have also used JumpCloud for event logs and for other similar activities to track our usage within the environment.
I have also used Okta quite a bit in recent roles but I think that JumpCloud is a very useful service, especially if you are just getting started. If you want to POC something, it is very useful and it is easy to set things up. I like that feature.
The issue of allowing SSH in the systems, managing users, their keys, etc. has been pretty useful to do with JumpCloud.
It is convenient to do the scripting part with JumpCloud though there are other tools that can do it too. They provide a lot of device profiling, etc. but I have not really explored those aspects extensively. It is a nice solution for both cloud access and system access.