[OPENAM-5252] DJLDAPv3Repo returns different error code when DN cache is enabled Created: 08/Dec/14  Updated: 20/Nov/16  Resolved: 11/Mar/15

Status: Resolved
Project: OpenAM
Component/s: idrepo
Affects Version/s: 11.0.2, 12.0.0
Fix Version/s: 11.0.4, 12.0.1, 13.0.0

Type: Bug Priority: Major
Reporter: Quentin CASTEL [X] (Inactive) Assignee: Quentin CASTEL [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: EDISON, release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

DN Cache enabled

Attachments: Text File DN_CACHE_TEST_UNIT.patch    
Issue Links:
depends on OPENAM-5241 DN cache is never enabled since OPENA... Resolved
Target Version/s:
Sprint: Sprint 77 - Sustaining, Sprint 78 - Sustaining
Support Ticket IDs:


NB : correct https://bugster.forgerock.org/jira/browse/OPENAM-5241 first

The DN cache could be corrupted : listener doesn't seems to work

How to reproduce the bug :

1) Read the attribute of a user => the DN would be in cache
2) Delete the user without using the OpenAM API => a call back should remove the DN from the cache
3) Read the attribute of the DN again => should throw an exception 223 (DN for this user can't be found)

I wrote a test unit attached to this ticket.

Comment by Quentin CASTEL [X] (Inactive) [ 06/Mar/15 ]

Concerning the unit test patch:

Unfortunately, it's not easy to write a test for testing the persistent search. The memory backend doesn't allow to add the persistent search.
You can ignore the unit test above as it will always fail: the persistent search is ignored so the cache won't be clean anyway.

For testing the issue, what you can do is:

  • Create a user "test" in OpenAM
  • remove it without OpenAM. You can use Apache Directory studio for example
  • Call the rest API:

curl --header "iplanetDirectoryPro: AQIC5wM2LY4Sfcyb.....*"\

You should see a 220 instead of a 223 error in the logs.

Comment by Quentin CASTEL [X] (Inactive) [ 11/Mar/15 ]

Fixed in 13.0.0 in r12960
Fixed in 12.0.1 in r12961
Fixed in 11.0.4 in r12962

Generated at Mon Oct 19 21:08:47 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.