# LDAP Setup for Discourse
**URL:** https://meta.discourse.org/t/ldap-setup-for-discourse/88349
**Category:** Self-hosting
**Tags:** discourse-ldap-auth
**Created:** [May 24, 2018, 7:34am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349 "2018-05-24T07:34:32Z")
**Posts on this page:** 15
**Page:** 2
### Author:  [@esepjav](https://meta.discourse.org/u/esepjav)
#### Post date: [May 29, 2018, 6:10pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/21 "2018-05-29T18:10:54Z")
which jira?
git clone [GitHub - ShaohuaSmile/discourse-jira: Automatically translate JIRA id to a hyperlink to JIRA issue · GitHub](https://github.com/ShaohuaSmile/discourse-jira.git)
git clone [GitHub - Jake-Shadle/discourse\_jira: Discourse Onebox plugin for JIRA · GitHub](https://github.com/Jake-Shadle/discourse_jira.git)
---
### Author:  [@esepjav](https://meta.discourse.org/u/esepjav)
#### Post date: [May 29, 2018, 6:23pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/22 "2018-05-29T18:23:30Z")
Thanks so much for your support.
I removed abbreviation plugin from app.yml and do rebuild.
The problem is solved. we can see login with ldap button.
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [May 29, 2018, 7:11pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/23 "2018-05-29T19:11:37Z")
@dnsmichi, @Falco
A Million thanks for all your help and your support 🙂
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [November 22, 2018, 8:44am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/24 "2018-11-22T08:44:54Z")
Hi,
our Discourse version is :Discourse 1.9.0.beta1
Last night, I have changed Discourse certificate from Symantec certificate to DigiCert, then rebuild the Discourse, and app is running, but LDAP button is no longer appear in home page (after clicking on “Log In” button).
But, it is possible to login to Discourse with “[https://discourse.xx.xx.in/auth/ldap](https://discourse.xx.xx.in/auth/ldap)”. Could you please let me know if any one has any idea on this.
Got the below error in the F12 browser console.
we have below plugins in app.yml
```plaintext
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/Axel-Naumann/discourse-jira.git
- git clone https://github.com/jonmbake/discourse-ldap-auth.git
```
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [November 22, 2018, 11:30pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/25 "2018-11-22T23:30:49Z")
You are on an obsolete Discourse version with security exploits. You should update to 2.1 ASAP
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [November 23, 2018, 8:55am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/26 "2018-11-23T08:55:49Z")
Hi @codinghorror,
Thanks so much for the response. We will look forward to upgrade to 2.1.
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [November 28, 2018, 5:13pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/27 "2018-11-28T17:13:22Z")
Hi,
I would like to upgrade Discourse to v2.1.2. My current version of postgres database is 9.4. Before upgrading the Discourse , is it necessary to upgrade database to higher version (10+) ? Could you please confirm.
Thank you.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [November 28, 2018, 5:21pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/28 "2018-11-28T17:21:26Z")
Yes, we only support Postgres 10+. If you followed our standard installation instructions, the upgrade will be handled automatically.
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [November 28, 2018, 5:55pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/29 "2018-11-28T17:55:43Z")
Hi,
Thanks the for the response. But, I connect to database that is in separate VM, but not in same VM. (configured external database details in app.yml file).
So, I first I will need to upgrade the postgres to 10+ first ? and then go for Discourse upgrade ?
Could you please correct me, if you were referring standard installation instructions at [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) or some other ?
Thank you.
---
### Author:  [@ssvenn](https://meta.discourse.org/u/ssvenn)
#### Post date: [November 28, 2018, 7:02pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/30 "2018-11-28T19:02:42Z")
Did you install postgres yourself or did you split the discourse setup into separate web and data containers with the included templates?
Have a look at [GitHub - discourse/discourse\_docker: A Docker image for Discourse · GitHub](https://github.com/discourse/discourse_docker) , it explains how the different templates work. If you installed postgres outside of the Discourse templates, it is probably safest to backup your Discourse, verify that you can load it on a separate standalone instance before attempting to upgrade. Then if the upgrade in-place fails you know you can at least start over with a blank deploy with separate data and web containers and load your data from backup.
---
### Author:  [@pprp](https://meta.discourse.org/u/pprp)
#### Post date: [November 29, 2018, 9:10am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/31 "2018-11-29T09:10:08Z")
Hi,
Thanks for the response.
I have only one container (app), in VM where Discourse is installed. I have database in separate VM (PostgreSQL installed in this VM and also database created in it).
I have mentioned the database details in **/var/discourse/containers/app.yml** as like below:
```
DISCOURSE_DB_SOCKET: ' '
DISCOURSE_DB_USERNAME: 'name'
DISCOURSE_DB_PASSWORD: 'pwd'
DISCOURSE_DB_HOST: 'database host name'
DISCOURSE_DB_PORT: '5440'
DISCOURSE_DB_NAME: 'database name'
```
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [September 28, 2023, 11:06pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/34 "2023-09-28T23:06:49Z")
---
### Author:  [@JustinZ](https://meta.discourse.org/u/JustinZ)
#### Post date: [February 13, 2025, 6:02am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/35 "2025-02-13T06:02:47Z")
I get an error in the latest Discord upgrade if this plugin is enabled in the app.yml:
```plaintext
Gem::ConflictError: Unable to activate omniauth-ldap-1.0.5, because omniauth-2.1.2 conflicts with omniauth (~> 1.0) (Gem::ConflictError)
```
---
### Author:  [@steffzt](https://meta.discourse.org/u/steffzt)
#### Post date: [February 25, 2025, 10:49am UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/36 "2025-02-25T10:49:15Z")
Well, at least, I am not alone. 😉
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 15, 2025, 9:25pm UTC](https://meta.discourse.org/t/ldap-setup-for-discourse/88349/37 "2025-09-15T21:25:33Z")
Did this ever get resolved? Is anyone still using this? (Looks like there was an update a few days after the last message, so maybe all is well?)
[Previous page](https://meta.discourse.org/t/ldap-setup-for-discourse/88349.md?page=1)