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

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
  • Thanks for your answer, but the mapping is not the Problem. This part I did according the manual already. The problem is, that they are not written to the target System, neither with an adHoc Projection nor directly with the integrated Target System browser which you can start from within the SyncEditor (Tab: Configuration -> Target System -> Browse...).

    From the target system browser, a standard attribute is written immediately to the directory. If I change an attribute which is assigned via an auxiliary class, then this attribute is not updated in the directory.
Reply
  • Thanks for your answer, but the mapping is not the Problem. This part I did according the manual already. The problem is, that they are not written to the target System, neither with an adHoc Projection nor directly with the integrated Target System browser which you can start from within the SyncEditor (Tab: Configuration -> Target System -> Browse...).

    From the target system browser, a standard attribute is written immediately to the directory. If I change an attribute which is assigned via an auxiliary class, then this attribute is not updated in the directory.
Children
No Data