You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Igor Bondarenko <je...@users.sf.net> on 2014/05/13 11:01:19 UTC
[allura:tickets] #7387 Allura's LDAP provider improvements
---
** [tickets:#7387] Allura's LDAP provider improvements**
**Status:** in-progress
**Milestone:** limbo
**Labels:** 42cc
**Created:** Tue May 13, 2014 09:01 AM UTC by Igor Bondarenko
**Last Updated:** Tue May 13, 2014 09:01 AM UTC
**Owner:** nobody
Followup to [#7342]
When LDAP auth enabled:
- implement `update_notifications` on provider (it should do nothing and return '', as local provider does).
- `/auth/do_login` raises, when trying to login with **valid** username, but **empty** password (should show invalid login error, I guess)
- seems like we also need to use [ldap.dn.escape_dn_chars()](http://www.python-ldap.org/doc/html/ldap-dn.html#ldap.dn.escape_dn_chars), when constructing DN's from username.
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7387 Allura's LDAP provider improvements
Posted by Dave Brondsema <br...@users.sf.net>.
- **status**: code-review --> closed
- **QA**: Dave Brondsema
- **Milestone**: limbo --> forge-may-30
---
** [tickets:#7387] Allura's LDAP provider improvements**
**Status:** closed
**Milestone:** forge-may-30
**Labels:** 42cc
**Created:** Tue May 13, 2014 09:01 AM UTC by Igor Bondarenko
**Last Updated:** Mon May 19, 2014 01:19 PM UTC
**Owner:** nobody
Followup to [#7342]
When LDAP auth enabled:
- implement `update_notifications` on provider (it should do nothing and return '', as local provider does).
- `/auth/do_login` raises, when trying to login with **valid** username, but **empty** password (should show invalid login error, I guess)
- seems like we also need to use [ldap.dn.escape_dn_chars()](http://www.python-ldap.org/doc/html/ldap-dn.html#ldap.dn.escape_dn_chars), when constructing DN's from username.
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7387 Allura's LDAP provider improvements
Posted by Igor Bondarenko <je...@users.sf.net>.
- **status**: in-progress --> code-review
- **Comment**:
Fixed in [#7388]
---
** [tickets:#7387] Allura's LDAP provider improvements**
**Status:** code-review
**Milestone:** limbo
**Labels:** 42cc
**Created:** Tue May 13, 2014 09:01 AM UTC by Igor Bondarenko
**Last Updated:** Tue May 13, 2014 09:01 AM UTC
**Owner:** nobody
Followup to [#7342]
When LDAP auth enabled:
- implement `update_notifications` on provider (it should do nothing and return '', as local provider does).
- `/auth/do_login` raises, when trying to login with **valid** username, but **empty** password (should show invalid login error, I guess)
- seems like we also need to use [ldap.dn.escape_dn_chars()](http://www.python-ldap.org/doc/html/ldap-dn.html#ldap.dn.escape_dn_chars), when constructing DN's from username.
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.