Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-15337

Naming strategy for IDM with embedded DJ and explicit table repo does not work anymore

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not a defect
    • Affects Version/s: 7.0.0, 7.1.0
    • Fix Version/s: 7.0.0, 7.1.0
    • Component/s: Module - Repository DS
    • Labels:
      None
    • Environment:
      IDM 7.0.0
      IDM 7.1.0-SNAPSHOT
      DS 7.0.0

      Description

      Our automated tests discovered failing tests for IDM with Embedded DJ and explicit table repo using a Naming strategy.

      https://ci.forgerock.org/job/IDM-7.0.x/job/full_linux_embedded_dj_explicit_table/88//artifact/report.html#totals?critical

      The last working state was in mid May 2020 with the IDM snapshot using DJ Milestone 6.1, however with older IDM build commit a3c3e98fc89a3c967bb67cdc9e53750a0aa3ac49 and DJ Milestone 7.2 it was working.

      Affected automated tests could be run as:

      ./run-pybot.py -s *repository.opendj.naming_strategy* OpenIDM
      

      Steps to reproduce:

      • Install IDM with embedded DJ explicit table, before starting make sure there is no namingStrategy in repo.ds.json under resourceMapping.explicitMapping.genericMapping.managed/user
      • Start IDM up and create a managed user
        curl -H "X-OpenIDM-Username: openidm-admin" -H "X-OpenIDM-Password: 
        openidm-admin" -H "Content-Type: application/json" --request  POST 
        --data-binary {"userName":"default", "givenName":"barbara", 
        "sn":"jensen", "mail":"default@example.com",                       
        "telephoneNumber":"555-123-1234", "password":"TestPassw0rd", 
        "description":"New user"} http://localhost:8080/openidm/managed/user/?_action=create
        
      • Then run ldapsearch to check the user was created in LDAP
        ./ldapsearch -h localhost -p 31389 -D "uid=admin" -w 5up3r53cr3t -b "dc=openidm,dc=forgerock,dc=com"  "(cn=default)" dn
        
        The LDAP bind request failed: 13 (Confidentiality Required)
        Additional Information: Rejecting a simple bind request because the password policy requires secure authentication
        

        Attachments

          Activity

            People

            Assignee:
            brmiller Brendan Miller
            Reporter:
            son.nguyen Son Nguyen
            QA Assignee:
            Son Nguyen Son Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: