Hi, related to the other bug, the only workaround was to remove the attribute and add it again in the schema handling.
The issue is that when this process takes place the attribute mapping is not recognized at all in the provisioning process. For example, let's say that after the initial import of an ldap resource profile, everything works fine. Then we delete the attribute name (Distinguished name) and we create it again in the schema handling with the same outbound mapping. Now, attempting to create an account in the resource for a user, the Distinguished name field gets a blue and a red star (indicating value missing I guess ) and clicking save on the account results in a 'Distinguished Name' is required error message.
In general the resource schema editing seems problematic from the UI. On a side note is it possible to edit the XML files directly ?Or should the original file be edited and re-imported?