[MGNLLDAP-21] Install/Update: add configuration for ExternalUserManager Created: 10/Dec/07 Updated: 24/Jul/17 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | LDAP Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Vivian Steller | Assignee: | Sameer Charles |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
On installation or update currently one has to add the ExternalUserManager manually. This could be avoided by adding an Install Task. |
| Comments |
| Comment by Vivian Steller [ 10/Dec/07 ] |
|
this issue can only be resolved if LDAP is a module, see |
| Comment by Vivian Steller [ 04/Mar/08 ] |
|
ensure that the external user manager is ordered BEFORE the admin user manager. Otherwise, in some scenarios (especially if you duplicate LDAP users w/o password in Magnolia) activation will fail. |
| 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. |