Update connector to work with SharePoint 2013.

A change was made to the domain casing so that they are consistent, in this case I added .ToLowerInvariant() to user.Domain (AccountNameToDistinguishedNameAdapter.cs, Line 43)
As i mentioned this might not be applicable to all sites, so an option to enable/disable would be appropriate. Possibly also an option to select between Upper or Lower case might be useful too.

As per Dustin Page from ASC:

Hi Andre,

Looks like I found the issue, one of the guys made a change to the SQL server environment in Production a few weeks ago and forgot to set all the database collation types back properly. I did move it back to what it’s meant to be set to but it seems I’m still getting the following error in the logs;

20120914,05:25:47,Connector processing failed.,Connector Processor,Information,"Connector Processing page 1 for connector Aurion Schedule Connector failed with reason Cannot resolve the collation conflict between ""SQL_Latin1_General_CP1_CI_AS"" and ""Latin1_General_CI_AS"" in the equal to operation.. Duration: 00:00:01.5635366

SQL collation is set back to SQL_Latin1_General_CP1_CI_AS as per the test environment. Yet I’ve restarted the Broker Service and it keeps seeing the same error?

Marked as critical because I have been requested to have an answer by 1pm Brisbane time.

E-mail from Peter Williams:

"There technical guy Andrew Stewart will be on the call. I spoke with him this morning and he had a detailed technical question about setting up the Aurion connection. Can you please try to have an answer for this by the meeting today.

Question: What type of account does the Identity Broker for Aurion connect to in Aurion? Is it an employee self-service (ESS) account or is it a client account?"

Preparation question from a client:

Aurion has 2 API types, xml rpc and xml document binding or such. Which does Unify need for their broker?

I know we've dealt with this question before, but I couldn't find the answer on here or in the documentation.

Restarting the service to enable WCF tracing is a PITA.

Might be possible to do something like mentioned in this thread:
http://stackoverflow.com/questions/4041289/change-switchvalue-on-trace-listener-in-runtime

Or:
http://stackoverflow.com/questions/7795614/can-i-control-wcf-tracing-programmatically

Connector and transformation post handling does not currently handle validation errors correctly. If custom view data is invalid, the post engine will attempt to access the next sink or stream source. Instead, they should be configured to redirect to the same step of the process.

With Unify Identity Broker 4.0 & 4.1 we can configure Windows Event Log Writer to write to a custom log: https://unifysolutions.jira.com/wiki/display/IDB41/Windows+Event+Log+Writer

Will Unify Identity Broker create the custom log when we configure this and if so do we have to restart the server or what steps must be taken as it is not stipulated.

Required for health check data collection scripts.

Can someone please point me in the right direction of an explanation as to what section I need to configure to set the polling interval? I recall this used to be calculated in ticks for version 2., but I can't see the equivalent in the default 3. config file, and my JIRA searches ("connectorconfigurations", "connector interval", ...) are coming up blank so far.

Although the navigation has been improved with Back buttons and the Dynamic Sitemap (breadcrumbs), this is only navigation "backwards", there are still a number of problems going forward:

1. It is difficult to tell what buttons do
2. There is no standardized forward navigation process to related components and subsets of a component
3. Realestate is used poorly, and movement through the website requires a lot of scrolling

Solution:

To remedy this, the following is a suggested set of fixes:

1. Include a set of links (tabs) to the left of every page that define navigation within the component or context being viewed. (e.g. Connector details would have Schedules, Schema, Timings, General tabs etc.)
2. Each page would have a drop-down collection of operations for the component or context being viewed. (e.g. Connector details would have Add Schedule, Enable, Execute Full import etc. etc.)

Benefits:

This would achieve all of the listed problems above, but would also help with:

1. Standardization of display components, leading to reusable Web components which benefits every product and every plugin.
2. Standardization of navigation, to allow for components like the EB/IDB security to apply business logic to each context.
3. An entry point for plugins to add Navigation and Operations. (e.g. FIMEngine.dll adds a FIM tab to adapters)
4. Helps with localization by reducing the noise in views.

Ultimately the overall result would be that I would be able to say "Now run a Full Import" and it would be intuitive that it's in the drop down, as opposed to "Now scroll down to where it says Full Import, then find the table icon with the green refresh icon and click that"

As discussed. The add transformation button should add to the end of this list of transformations, using the context of the final transformation.

Additionally, there will have to be buttons for each transformation to add a transformation previously, to allow for adding a transformation to the end.