[MGNLLDAP-101] LDAP tester is broken after introducing the cache into LDAPUserManager Created: 23/Jan/17  Updated: 27/Jan/17  Resolved: 26/Jan/17

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

Type: Bug Priority: Neutral
Reporter: Jan Haderka 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
Sprint: Kromeriz 80
Story Points: 5

 Description   

Fix:

  • Disable cache for ldap tester
  • info.magnolia.jaas.sp.ldap.LDAPUserManager#loadProperties should use methods info.magnolia.jaas.sp.ldap.LDAPUserManager#getItemFromCache and info.magnolia.jaas.sp.ldap.LDAPUserManager#addItemIntoCache which checks if cache is not disabled and are failsafe if ldap-user-manager-cache can't be initialized
  • Add missing dependency to cache-core into ldap-tester pom
  • Put back info.magnolia.ldap.tool.ShadeSmoker which is used to trick the shade-plugin (to not remove ldap module classes when they are not referenced directly from code and minimizeJar property is set to true)

Improvements:

  • use user.dir instead of hardcoded /tmp folder
  • set realmName for userManager
  • add unit test for Tester

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