Gold Coast City Council has asked whether an upgrade of Oracle from Version 9 to either 10g or 11g will have any impact on Identity Broker for chris21. It is presumed that there is NO associated upgrade to the chris21 application version.

The field "Telphone" is multivalue, and the following line is being imported:

13,Matthew Clark,1337,"0413371337,0412123123",another@address.com

However, the Telephone value is still being sent to FIM as a single valued field:

dn: CN=859cbd1d-fe77-4cd7-b88d-998f12aae491
objectClass: csvPerson
IdBID: 859cbd1d-fe77-4cd7-b88d-998f12aae491
Key: 13
Name: Matthew Clark
EmployeeID: 1337
Telephone: 0413371337,0412123123
Email: another@address.com

It's pretty easy to miss the fact that you have to update the connector after the schema is updated, a yellow bar similar to that used in the standard warnings above the schema mappings would help this.

The error from Chris21 is passed straight through to the IdB UI and displays the password.
I don't think this is desirable.

Enable the connector to fetch the names of available Chris21 forms on configuration. We could use the scripted dropdown control so that it does not become cumbersome to navigate the hundreds of forms available by default.

Estimate includes restructuring the UI for the required multi-step approach, and research into how to retrieve form details via GTR.

The Service Account user is not created in the Database and therefore the service cannot start. I would expect that the user would be created if the database is being created.

Because of the use of the GetObjectClass method which uses an object's DN to work out which schema it should use, new objects are not found for added entities exported to the adapter. The following error is thrown:

For adds, the adapter should be checking for the presence of the objectClass attribute exclusively (which is present in the LDIF).

After adding a schema field with the same name as an existing field using a relational and date relational transformation, I was unable to modify any transformations, with the reason being "An item with the same key has already been added". Manually removing the transformation from the config and restarting the service resolved the issue.

If you add a "Length" search term using the UI in the Entity Search, it clears the other search terms and does not search.

An import against a connector with entities that fail validation will generate changes even for those failing entities.

My setup currently has two connectors:

• e5d00f42-3725-4897-b909-73149f22c8cd (tony)
• 69e858d9-ef5e-488b-88cb-a75f3a8a1ed5 (AR)

One adapter:

• b78abc46-dc95-40d8-a2ef-37fcf2986e82 (AR Adapter)

An import against AR generates 20 changes for the 20 entities that are failing validation.

Each time, 20 entries appear in the changes table, with entity id's that cannot be found elsewhere in the database.