-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ldap authentication not working after restoring backup in discourse #40
Comments
@esepjav Is there an error in the server log? If so, can you post it? |
where I can find ldap logs? |
https://meta.discourse.org/t/where-are-all-the-discourse-logs/58022... If you can login with a non-ldap user, The logs web UI will probably display the error stack trace. Otherwise, the next best place to check [on the server] is The Rails / Unicorn logs. |
We noticed that the table “user_emails” is empty for some users and they don’t show up in query “Active users”. |
That stores email addresses of users: https://github.com/discourse/discourse/blob/acd1693dac1bff6ff50250d942134bc48a27ff14/db/migrate/20170717084947_create_user_emails.rb. I believe email address is required so there should be at least one entry for each user. |
We found that "users" table when is imported to staging, "email" filed is not there any more and table "user_emails" doesn't have all data from production, so we want to write script to get all data from "users" table in production and compare with "user_emails" table and add missing one. do you have any comment? |
Also we found in discourse name has username info but we want to have real name for name. |
Hi,
We have discourse production 1.9.0 with ldap plugin from https://github.com/jonmbake/discourse-ldap-auth.git commit ccf5e36 (0.3.0).
We restored data from production to our staging server which is 2.2.0 discourse version with recent ldap plugin (0.4.0).
Unfortunately we are not able to authenticate with ldap even if ldap setting is same as before.
Please support.
The text was updated successfully, but these errors were encountered: