RESOLUTION 1
1- Modify the Exchange to Notes connector using the Advanced Settings
2-In the Provision Attributes section Add the following Map:
Target Attribute: FullName
Source Attribute: Mail
Repeat the same for Update Attributes
4- Save and Activate the Configuration
5- Edit the configuration.xml
6- Locate the Connector by Name
7- Locate the <Resources>false</Resources> line
8- Add the following test under the line found above.
<AppendAttributes>FullName</AppendAttributes>
9- Save and close the configuration.xml file.
10- Run the Connector.
RESOLUTION 2
Add it to the bottom of the Username field:
1- In an existing Active Driecory to Notes connector(or new) > Advanced Settings > Users > Update Attributes
2- Add Rule: Target Attribute "cn"
3- Pick a source attribute that has the desired email address you want to push to the bottom of the USERNAME field.
If source has SMTP: or smtp:these needs to be removed. If the source attribute is "mail" everything is fine, if the source attribute is "TargetAddress" then you need to use substring starting at 5 and going to a large number.
Use "mail" as that's the simplest example.
4- Save configuration
5- Close the configuration GUI
6- Go to the configuration.xml (main) in the config for the connector you are modifying and add this tag:
<AppendAttributes>cn</AppendAttributes>
First sync, the tool creates the object without the address at the bottom. This is due to limitations of the LDAP connector, when the tool passed the information to LDAP to create the object it adds the Plain user name at the end of the list, independent of any order the tool gives it the data.
The second sync will update the object USERNAME field with the address in the update attributes and since the tool added to the APPENDATTRIBUTE tag in the config for that connector, the Notes sync will append the CN in the update configuration to the user at the end.
If the tool tried to directly make that change, it would get an illegal operation error where the tool would try to replace the entire CN and that would be illegal. The way the tool does it in this setup is that it appends data to the already created CN on the object during the second pass.
