LDAP Setup for Discourse

Which version of Discourse is installed?

Installed version:

v2.0.0.beta10 +230

So it looks like you are using a third-party plugin that is broken. And it’s not the LDAP one.

Can you try safe-mode ?

1 Like

Hi,
I think we might have modify site_setting.yml to be able to see login with ldap button.
Do you know any idea?

We don’t have that in our setup. The JS error should be solved, that’s probably causing the page to not render properly.

@pprp
Please share the installed plugin lines from your app.yml and any modifications you’ve made to your theme with custom JS in the header, footer, etc. sections.

Plugins go here

see Install Plugins in Discourse for details

hooks:
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/Jake-Shadle/discourse_jira.git
- git clone https://github.com/PoloGT/abbreviation-discourse-plugin.git
- git clone https://github.com/jonmbake/discourse-ldap-auth.git
- git clone https://github.com/ShaohuaSmile/discourse-jira.git

where is files for " your theme with custom JS in the header, footer, etc. sections." ?

Not sure why you are answering instead of @pprp here, is that a colleague of yours?

yes I am his colleague.

1 Like

I’d say you disable the jira and abbreviation plugins one by one and try to eliminate the error (each line removal with an app rebuild). Those plugins look dated, last commit was 2016. Not sure if they’re still compatible with Discourse, nor if they’re supported.

The abbreviation and jira onebox plugins for example were moved to #plugin:broken-plugin in 2016.

Theme customization happens in the frontend in your admin console, /admin/customize/themes. I doubt that this helps though as you’re using plugins which seem broken.

which jira?
git clone https://github.com/ShaohuaSmile/discourse-jira.git
git clone https://github.com/Jake-Shadle/discourse_jira.git

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.

6 Likes

@dnsmichi, @Falco

A Million thanks for all your help and your support :slight_smile:

1 Like

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”. 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

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

You are on an obsolete Discourse version with security exploits. You should update to 2.1 ASAP

2 Likes

Hi @codinghorror,

Thanks so much for the response. We will look forward to upgrade to 2.1.

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.

Yes, we only support Postgres 10+. If you followed our standard installation instructions, the upgrade will be handled automatically.

2 Likes

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 https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md or some other ?

Thank you.

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

2 Likes