-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support for 3.0? #36
Comments
So take this at a grain of salt for your use case but I have gotten this plugin to work on taiga v 3.0. Since I was setting up a new tiaga instalation with a new ldap server so I had no data to migrate between versions. I am also using new small openldap server with 2 users. But I had no errors in the instaltion of this plugin so it may work in your case |
I cannot authenticate using this module in the current taiga version. I've done all described in the readme. LDAP_SERVER and LDAP_SEARCH_PROPERTY. Until now, I've got some applications using ldap, but all they need was something like ldap_bind_dn, ldap_bind_password, ldap_search_base or the ldap_port. So here I'm using the same settings but for the two properties mentionend above, I can not compare to the settings of the running apps. I would like to use the email address as username. I've tried it with:
Am I missing something? |
Here is my working LDAP config for 2.0: LDAP_SERVER = 'ldap://nis.domain.local' LDAP_EMAIL_PROPERTY = 'mail' On 10/13/2016 12:39 PM, Leo wrote:
|
@mroe1234 so you are using your user names to login, in my case i would just change that to mail. Right now I'm also set it to uid for testing purposes. Where is this "nis" comming from ('ldap://nis.domain.local'). I've left it on 'ldap://ldap.domain.local'. Can I somewhere look that up? |
yes, you can change the attribute you want to use for 'username' to whatever you want. On 10/13/2016 01:46 PM, Leo wrote:
|
yeah, okay got it. Was the LDAP_SERVER property, so authentication via uid is working but not using mail. Have you ever tested it via mail? |
Yes this is a known issue: #18 |
@flyingcircle no not really. As I see, this issue is about invitation email. I'm talking about to use LDAP_SEARCH_PROPERTY = 'mail' instead of the username. So that each user should use his ldap email as username to log in. I will open a new issue for that. |
I see @lorsulic opened #37 for their issue. As to OP, it works for us using Taiga 3.0 and taiga-contrib-ldap-auth v0.1.1. This is a direct installation of Taiga 3.0, though, not an upgrade from 2.0. @mroe1234 I guess I'd also recommend using |
Before I start my upgrade, should this plug-in work with 3.0?
The text was updated successfully, but these errors were encountered: