The definition about "console" is a bit unclear. I had no clue until Tony explained what it is referring to,
"it writes to the console if you're debugging Identity Broker through the console at:

C:\Program Files\UNIFY Solutions\IdentityBroker\Services\Unify.Service.Connect.Debug.exe"

I think it could be a good idea to add some detailed information on the page just to make it clear for everyone.

Cheers,
Sam

SCOM integration capability for consumption in EB 3.1 and IdB 4.1

System administrators prefer to observe activity and errors through existing monitoring tools, such as SCOM. The value of Event Broker (and our entire product range) in an Enterprise would be greatly improved by permitting this.

There is currently no character field in Identity Broker. This is currently worked around by storing those values in the StringValue field:

GET: entity.GetValue<StringValue>(...).Value0;
SET: entity.SetValue<StringValue>(character.ToString(...));

However if this won't take much time it might be more descriptive to include a character field type.

The service installer should configure the web engine settings for FIM Event Broker and Identity Broker.

Consider stopping ActionRefresh when the page isn't focused as it would reduce network usage.

If you create a Custom Log Writer with the same display name as an existing one it goes back to the Logs page with an error "A log writer already exists with the name "BlahBlahBlah" " You lose any configuration. Could be good to validate first.

We should investigate whether we can use phantom query strings to prevent the use of the CSS/JS cache when upgrading to new product versions. See: http://davidwalsh.name/prevent-cache

Though RFC4180 states the end of each row should be CRLF, some CSV files I've encountered (such as from here: http://www.ourairports.com/data/) use the lone, Unix/OSX LF at the end of rows. Our CsvEnumerable is intended to parse these but currently doesn't

The WCF communicator is currently only able to use Windows credentials. Update the communicator information to have auth type, then switch on that to set either the Windows or the UserName credentials.

The v5.0 release supports provision/sync of only users and groups. I am not clear about the use case(s) as to where Broker would be used in lieu of AADConnect (or DirSync before it) or the WAAD connector in FIM - but without support for contacts such an interchange could not be considered for most enterprises.