The ability to write directly to the Identity Broker logs - such that any Broker log writer can be employed to pick this up apart from the default - is highly desirable.

Such a feature would avoid the need for the current practice of logging to custom log files using either custom code or various logging libraries.

Presently debugging a PowerShell connector script requires extensive use of logging.

While the above is still going to be necessary, the ability to attach a PowerShell ISE session to a PowerShell process to allow step-throughs and breakpoints is highly desirable.

The delta import functionality on the SQL connector requires a "Modified" column be present in the database, as a DateTime.

If the schema provider doesn't have this column, the "Poll Changes" operation on the connector should be disabled. Currently it just throws an error:

Chris21 full import is getting partway through and then blocking - no errors thrown, just doesn't complete.

It's only processing 23,000 entities out of a total of 114,000.

Noticed today that if you've got a database connector, and the account you're connecting with has access to the database but no roles assigned (db_reader etc) then a request schema will not show an error - it will instead show that there are no schema fields.

Test agent completes without issue.

The only way to show the error (no SELECT permission), you have to manually add a schema field and attempt an import.

The schema provider should display this same error when attempting to get the schema.

I have a PowerShell connector that is pulling two attributes, DN and another one. DN is the key and it's throwing errors saying "An item with the same key has already been added". This isn't possible because DN is unique. Here is the Import All script:

import-module ActiveDirectory

$server = "Dcbr2wdc1"

$searchBase = "ou=Users,ou=dams,dc=internaldmz-dev,dc=local"

$users = get-aduser -Server $server -SearchBase $searchBase -Properties DistinguishedName, msDS-UserPasswordExpiryTimeComputed -Filter {PasswordNeverExpires -eq $false}

foreach($user in $users)

{

$entity=$entities.Create()

$entity["ADDN"] = $user.DistinguishedName

$entity["ComputedPasswordExpiry"] = $user.'msDS-UserPasswordExpiryTimeComputed'

$entity.Commit()

}

and here is the schema

New-Field 'ADDN' 'string' $true $false $true;

New-Field 'ComputedPasswordExpiry' 'string' $false $false $false;

# name type key read-only required

I tried writing the DNs to a file in the script and just got a list of DNs, no obvious duplicate. Attached the log and connector config.

Can we get more information in error messages. An example is today, in a connector, I'm getting the error: 

"An error has occurred: An item with the same key has already been added."

This is all the information I'm getting and though it tells me what the error is it doesn't give me any information that helps me resolve it. What would be useful is if it provided the key that it's faulting on.

I have an adapter that is a position type that has a field for the ReportsTo position. I'm generating a DN on this field. I've got bad data here so it wouldn't be able to resolve the DN. My question is, should this prevent the entire adapter from loading in changes. Right now I've got 19 changes and 0 entities and this error being thrown. Does the bad DN reference prevent the whole thing from loading?

This is the error I'm getting:

I've created an adapter and only just had the connector populated. The adapter shows >1000 entities but when I click on the link to go to the Entity Search, it sits at Processing for a few minutes and then the following pop-up appears. There's nothing about it in Event Viewer or the IdB logs

What is this error indicating and how do I resolve it?

I am having some connectivity problems in one of my agents that should be over SSL, not sure if it's unrelated.