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
- 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, please remove.