Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-246

Error in parsing LDIF file

Attach filesAttach ScreenshotWatch issueCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0-M31
    • 1.0.0-M32
    • None

    Description

      Hi Team,

      I would like to parse a simple LDIF file in which there's an empty-value attribute like below:

      dn: cn=Steven Nguyen,ou=SAP,dc=sap,dc=local
      changetype: modify
      replace: objectClass
      objectClass: top
      objectClass: user
      objectClass: person
      objectClass: organizationalPerson
      -
      replace: sn
      sn: Nguyen Linh
      -
      replace: url
      -

      I expect the LdifEntry after parsing would have the same but the result is a bit different:

      dn: cn=Steven Nguyen,ou=SAP,dc=sap,dc=local
      changetype: modify
      replace: objectClass
      objectClass: top
      objectClass: user
      objectClass: person
      objectClass: organizationalPerson
      -
      replace: sn
      sn: Nguyen Linh
      -
      replace: url
      url:
      -

      When I send the above LdifEntry to my AD host, it rejects with the error: 00000057: LdapErr: DSID-0C090B8A, comment: Error in attribute conversion operation, data 0, v1db1.
      With my original LDIF file, I could successfully import to AD host (the empty-value attribute will be removed from the entry as expected).

      Could you please have a look at this?

      Best Regards,

      Steven Nguyen

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            snguyen Steven Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment