Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-5252

DJLDAPv3Repo returns different error code when DN cache is enabled

    Details

    • Sprint:
      Sprint 77 - Sustaining, Sprint 78 - Sustaining
    • Support Ticket IDs:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                quentin.castel Quentin CASTEL [X] (Inactive)
                Reporter:
                quentin.castel Quentin CASTEL [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: