This topic has 2 replies, 2 voices, and was last updated 6 years, 5 months ago by Firos.

  • Author
    Posts
  • #9207
     Firos
    Participant

    OpenAM documentation says,

    “You can enable the DN cache when the underlying LDAP store supports persistent search and mod DN operations (that is, move or rename DN)”

    When rename a user(uid/cn) in OpenDJ, data will not be available using new uid/cn trough OpenAM API if we enabled “DN Cache”.

    So my doubt is, actually we need to disable “DN Cache” in OpenAM, if we use operations like change in uid/cn in OpenDJ using APIs.

    #9355
     Peter Major
    Moderator

    Maybe you are running into OPENAM-3693 instead? DN cache should get properly updated after moddn/modrdn operations when using OpenDJ.

    #9399
     Firos
    Participant

    Peter it looks like the issue OPENAM-3693.

    When rename a user(uid/cn) in OpenDJ, data will not be available using new uid/cn trough OpenAM API if we enabled “DN Cache”.

    If i disable “DN Cache”, it works perfectly.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?