[MGNLLDAP-103] Problem with cache during startup with task for adding a user role Created: 17/Mar/17  Updated: 01/Aug/17  Resolved: 24/Jul/17

Status: Closed
Project: LDAP Connector
Component/s: None
Affects Version/s: 1.7.1
Fix Version/s: 1.9

Type: Bug Priority: Neutral
Reporter: Ervin Vystup Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File startup-error.txt    
Issue Links:
relation
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
Date of First Response:
Sprint: Kromeriz 105, Kromeriz 106
Story Points: 2

 Description   

Created task in the versionhandler (for adding a extra role to user) fails during the startup because cache is not available but is requested. It causes an exception from Guice caused by the info.magnolia.jaas.sp.ldap.LDAPUserManager that requests the CacheModule.

What happens is that when you add a role to a user, the user is requested through the DelegatingUserManager. This iterates over the available user managers (in keySet order so no speciic order), when it requests the user from the LdapUserManager the usermanager tries to access the cache, which as this is during the startup is not available and cause Guice to throw a ProvisionException which causes Magnolia to stop.


Generated at Mon Feb 12 02:21:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.