• State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 96 subscribers
  • Views 12667 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Auxiliary Classes/Attributes within an LDAP Directory are not written to target

rolf.joggi
over 7 years ago

I've connected an LDAP Directory which syncs correctly with the standard attributes. But the auxiliary attributes are not written back to the target System. Even with the target System browser from within the synchronization Editor the auxiliary attributes are not written back to the System. I've connected d1im v7.1 (current Version) with the same user as we had before with the v6.1.2 Version. Therefore I guess it can't be an Access Problem. To I miss something concerning auxiliary attributes/classes and an LDAP Directory?

Thanks in advance
Regards,
Rolf

Parents
  • 0 over 7 years ago
    I just went through this myself and even though we hard-coded the aux objectclass in the value template and added it to the list it was still error'ing out (saying objectclass did not exist). This is for anybody else reading this solution (which works)...make sure you keep upper case on both objectclass and structuralobjectclass attributes, yes the case matters for this! =)
Reply
  • 0 over 7 years ago
    I just went through this myself and even though we hard-coded the aux objectclass in the value template and added it to the list it was still error'ing out (saying objectclass did not exist). This is for anybody else reading this solution (which works)...make sure you keep upper case on both objectclass and structuralobjectclass attributes, yes the case matters for this! =)
Children
No Data