# JumpCloud LDAP/SSO

**URL:** <https://meta.discourse.org/t/jumpcloud-ldap-sso/167408>\
**Category:** SSO\
**Created:** [October 16, 2020, 9:52pm UTC](https://meta.discourse.org/t/jumpcloud-ldap-sso/167408 "2020-10-16T21:52:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![D\_Lasa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/d_lasa/32/195165_2.png) [@D\_Lasa](https://meta.discourse.org/u/D_Lasa)\
**Post date:** [October 16, 2020, 11:20pm UTC](https://meta.discourse.org/t/jumpcloud-ldap-sso/167408/2 "2020-10-16T23:20:13Z")

</div>

Ok…I figured out our issue:

We were trying to both setup LDAP in Discourse & create an SSO plugin in JumpCloud. This is unnecessary. We did not need to create a JumpCloud plugin.

Presupposing the LDAP Plugin is installed on your Discourse instance, this is what we did that worked:

- Go to Admin Console \> Settings Plugins \> LDAP Plugin Settings
- Select "Is LDAP plugin enabled?
- ldap user create mode: auto
- ldap lookup users by: mail
- ldap hostname: [ldap.jumpcloud.com](http://ldap.jumpcloud.com)
- ldap port: 389
- ldap methos: ssl or tls or plain
- ldap base: ou=Users,o=OrganizationalID,dc=jumpcloud,dc=com
- ldap uid: mail
- ldap bind dn: uid=ServiceUserID,ou=Users,o=OrganizationalID,dc=jumpcloud,dc=com
- ldap password: ServiceUserID password
- ldap filter: (&(objectClass=person)(uid=\*)(memberOf=cn=GroupName,ou=Users,o=OrganizationalID,dc=jumpcloud,dc=com))

The effect of disabling our GoogleSSO, (once we got the LDAP working), is that our users do not see the Google sign in and are taken to a generic “LDAP Authentication” page.

Lastly, if this is against [community guidelines](https://meta.discourse.org/guidelines), please remove.

---

_[View the full topic](https://meta.discourse.org/t/jumpcloud-ldap-sso/167408)._