[MGNLLDAP-14] user password field with LDAP authentication Created: 08/May/07 Updated: 24/Jul/17 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | LDAP Connector |
| Component/s: | None |
| Affects Version/s: | 1.0-rc3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Yuanhua Qu | Assignee: | Sameer Charles |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
window XP /redhat linux |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
There is one defect that allows the admin to break the publish once we use LDAP authentication. After using LDAP with empty password field for that user, admin can still put something in the password field of that user, save that change. If the string in the password field is not the same as that user's password in LDAP, that user will fail in activating page. The defect is that admin can remove the string in the password field but won't be able to save the change. The password is still there after click on save. I have to switch back to JCR authentication, set password to be null for that user. Then switch back to LDAP. Since switch authentication need server restart, this problem is quite annoying to me. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |