The following error was thrown when attempting to provision a new user to the SharePoint Org Profile connector (which is not a ModifyAnchor connector, see IDBSP-44):

This was resolved by removing the creation of the Identity Broker ID from the provisioning logic, however, there may be solutions where this is a design requirement where no other uniqueness can be guaranteed at provision time. Regarding the above, the entity was being added, so no modify behaviour should be taking place. This behaviour either needs to be corrected, or a better error message put in its place (if there is a legitimate reason a modify operation is being attempted and failing with a null reference).

When certain errors occur within an Identity Broker for Aurion connector, the Management Studio circles continue to spin green instead of correctly turning red.

Configurating Identity Broker for Aurion write "ContactPhoneNo" back to Aurion system in Identity Broker configuration.
The configuration should be correct as there are times that I can perform update into Aurion system and other times I cannot.

Performed the following are the observation at various point of data flow:

1. In Aurion HR system the ContactPhoneNo = (09) 622 1123
2. Projected into Metaverse telephoneNumber = (09) 622 1123
3. Provisioned into AD MA cs telephoneNumber = (09) 622 1123
4. Exported to AD endpoint
5. Modified in AD endpoint telephoneNumber = (01) 111 1111 - change made in AD to flow back to Aurion
6. Imported into AD MA cs telephoneNumber = (01) 111 1111
7. Did a Full Sync
8. Updated Aurion MA cs ContactPhoneNo = (01) 111 1111
9. Exported Aurion MA
10. In IdB's Adapter entity search = ContactPhoneNo = (01) 111 1111
11. In IdB's Connector entity search = ContactPhoneNo = (01) 111 1111 - changed reflected in Identity Connector entity search as expected
12. In Aurion HR system Contact_Phone_Number = (09) 622 1123 - change did not update in Aurion system. In correct result

After several tried with failure the following error is found in the Identity Broker log file:

20101026,11:27:29,Save entities to connector failed.,Connector,Warning,"Save entities Count:1 to connector Aurion Person failed with reason Aurion API error -1: Specified item CONTACT_PHONE does not exist for function QUERY_TO_XML. Duration: 00:00:01.0585937
Error details:
Unify.Communicators.AurionApiCommunicatorException: Aurion API error -1: Specified item CONTACT_PHONE does not exist for function QUERY_TO_XML
at Unify.Communicators.AurionWebServiceApiCommunicator.RaiseExceptionOnErrorCondition(Decimal pStatus, String pMessage)
at Unify.Communicators.AurionWebServiceApiCommunicator.SetValue(String item, String value)
at Unify.Communicators.AurionApiFunctionBase.SetStringValue(String item, String value)
at Unify.Communicators.EmpUpdatePersAurionApiFunction.SetFunctionValues()
at Unify.Communicators.AurionApiFunctionBase.RunFunction()
at Unify.Communicators.AurionCommunicator.SaveEmployee(IAurionEmployee employee)
.
.
.

It could be that while Identity Broker is performing "getAllEntities" and I run "Export" profile in FIM may created a conflict or confusion with the Aurion API.

Here is Shane Day's thought on this error:

I've had another thought about this - the Aurion API only allows one concurrent transaction, therefore if you are attempting two transactions (a query, and an update) at once, the API gets confused. That's the source of that error.

I'm going to suggest that we put a mutex around operations with one Aurion instance to prevent this situation from occurring. It already cannot happen by two query requests as the connectors are all in the same connector group.

Full imports fail on CSV connectors when there are no existing entities in the connector.

Currently, the CSV connectors in Identity Broker for Aurion are single-keyed connectors of type StringValue.

As there is a small chance that the usage of these connectors at the Department of Finance will require composite keys, the connectors should be upgraded to support this possibility.

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.