[MGNLLDAP-86] Magnolia Install or Upgrade throws Exception if LDAPUserManager is registered Created: 27/Oct/14 Updated: 01/Aug/17 Resolved: 24/Jul/17 |
|
| Status: | Closed |
| Project: | LDAP Connector |
| Component/s: | None |
| Affects Version/s: | 1.6.3 |
| Fix Version/s: | 1.9 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Marcus Büttner | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Documentation update required: |
Yes
|
| Sprint: | Kromeriz 105, Kromeriz 106 |
| Story Points: | 2 |
| Description |
|
Installation of magnolia 5.3.4 throws the following exception when LDAPUserManager is registred. 1) Module instance for module [ldap] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available. 1 error 1) Module instance for module [ldap] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available. 1 error LDAPUtils tries to resolve the LDAPModule. But the LDAPModule is not available at this time. There is a null check in LDAPUtils but the Provider throws an exception if the module could be resolved. IMHO the result could never be null. |