Hi. Just a quick note to report some unexpected behavior (v1.0.6).
I've been tinkering with two resources, a MySQL database and an openLDAP directory with inetOrgPerson and posixAccount schema.
The only guaranteed unique field from the (OrangeHRM) MySQL resource is the key field, emp_number (an int data type). Within Syncope's Resources / Schema Mappings for the resource, the key field isn't provided as an option in the pulldown for External Attributes. It does get set to Username, however.
Now, the openLDAP wants a uid as a guaranteed unique value. (More precisely, it wants a DN that happens to include the uid.) The derived attribute (uid => username) in Schema was still not working out for me. So I decided to poke at this by adding to the MySQL resource's schema mapping uid => emp_firstname (Internal Attributes => External Attributes) which I'd expected would produce a string value in the uid fields. And, surprise! The derived attribute (uid => username) instantly popped to life. The next run of the sync task with the MySQL resource produced a complete set of (numeric) uids.
To test this again, I added uidNumber => username as another derived attribute. Again, it wouldn't populate automatically. I added uidNumber => emp_smoker (a smallint in the MySQL schema.) The column populated at the next sync with the MySQL resource.
Edward Siewick
