MichaelJ.83993 (Customer) asked a question.
Configuring JumpCloud LDAP as user directory without a local agent
Apologies if this has been asked and answered already. I'm trying configure Okta to use JumpCloud's LDAP as our user directory, and it seems that I would need to run the LDAP agent on a local machine to accomplish this. It seems cumbersome to have the agent running on a local machine while the LDAP and Okta are both cloud services accessible from outside our LAN or VPN. Is there a best practice for this sort of thing? Any advice or suggestions would be much appreciated. Thanks!
Hi @MichaelJ.83993 (Customer) , Thank you for reaching out to the Okta Community!
The current directory integration system works only with agents.
If JumpCloud supports it, you could consider implementing an inbound SAML implementation with JIT (just in time Provisioning) where it would be the IDP for those users.
https://help.okta.com/en-us/Content/Topics/Security/idp-inbound-saml-workflow.htm
That being said, the attribute mappings might be limited in that case.
The alternative is to consider an Okta to JumpCloud implementation:
https://support.jumpcloud.com/s/article/ConfiguringOktaDelegatedAuthority
If my answers helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.