In order to be able to contact Aurion in a hosted environment, the Connector needs to be able to specify a proxy. If this is not possible in a short time frame, let me know asap and I'll see if we can resolve it by bypassing the proxy. This invovles IT Security so may be a show stopper.

This currently effects: Broadband (Due: 30/6)
Will effect: ACMA / TGA

When specifying the schema for a CSV file, you cannot change what is the required / readonly fields to generate keys. The CSV file format is not always controllable as it can be system produced. Can you please allow the modification of the schema settings.

Identity Broker for Aurion currently supports only a few writeable fields, including phone numbers and email address. The list of allowable attributes should be expanded to include as many as possible - at the very least, all fields supported by the EMP_UPDATE_PERS function.

Can you confirm the config for setting the external_mail_type in the Aurion Security User. The API guide has:
1=MAPI,2=VIM,3=MHS,5=Compuserve,9=Active Messaging,10=SMTP/POP,11=Notes,20=VINES

Do I need to send 10 or are there translations in the Connector to take SMTP?

Thanks

Peter

Fairly niche scenario, but if someone gets promoted to the top level of an organization their manager field in AD is not cleared. This is probably a combination of both the script and the AD connector not correctly clearing fields, but could be looked at if we catch up on everything else.

Example: https://unifysolutions.jira.com/browse/ACMA-25

As expected it looks ok but actually using the field can be difficult because you can't see highlighted text and the cursor is off-centre. If we can't fix it it may be better to just revert it.

It should also use a fixed-width font if it doesn't already.

Review the default rule:

• https://unifysolutions.jira.com/browse/DWWA-4
• To ensure characters that should be stripped (possibly hypens, apostrophes, etc?) are done so

Current feedback from DWWA and Aurion Corp suggest this is going to be a difficult scenario to deal with in its current state. As such, we should consider including the DTC removal DLL in the LITE installer so that's it off by default and can be optionally removed/renamed to turn it back on (which will probably never happen). This would mean we should be doing all our testing with transactions turned off.

Currently when an email address is changed in AD, the new address is flowed back to the base person record in Aurion. Aurion Corp have informed us that field is actually for personal emails. Instead, they would like us to, if possible, create a new Security User account for them and set its email.