+1
Answered

Entity in IdB connector and adapter but does not exist in target directory

Carol Wapshere 3 years ago in PowerShell connector • updated by anonymous 3 years ago 3

IdB 5, Powershell connector, target system is RedHat LDAP.


There are three objects which exist as entities in the IdB connector and adapter but do not exist in LDAP. FIM is trying to update them and we're getting "Object does not exist" errors back from LDAP.


Connector Full Imports have been run. I turned on the verbose logging I'd added to the script which lists the DN of every object found by the Import script and these objects are not listed. I can't see any errors in the IdB log and the Full Import appears to have completed successfully.


So the question is, if they were not imported in a connector full import, shouldn't the entities have been removed from IdB?

Affected Versions:
Fixed by Version:

Answer

Answer
Answered

Looking at the logs shows that there were exported entities during the full import. The import logic is designed to not delete entities that are added whilst an import is occurring, as it has no way of knowing whether the end system is omitting the entry because it was deleted immediately or because it’s just not available yet for the import (e.g. snapshot or read copy/write copy style systems).

Under review

Hi Carol,


Are you able to attach (or send through) the logs and let us know how many objects you're expecting? Has your configuration changed since the import (e.g. change in key)? Is there anything different about these objects (e.g. duplicate key)?


Thanks.

The primary key is the LDAP DN however that is actually set from the FIM side as part of provisioning. Nothing of that DN exists in LDAP, so either was never provisioned or got deleted somehow. (We are in Dev so weird things do happen). The key has not changed.

The main thing that is different is they're new user types being introduced in this phase (Shared and Generic accounts) so there could have been something wrong with the provisioning logic at some point. I just don't understand why the connector Full Import doesn't clear out the entities, giving FIM a chance to try re-provisioning them.

I'll send through some logs - Thanks.

Answer
Answered

Looking at the logs shows that there were exported entities during the full import. The import logic is designed to not delete entities that are added whilst an import is occurring, as it has no way of knowing whether the end system is omitting the entry because it was deleted immediately or because it’s just not available yet for the import (e.g. snapshot or read copy/write copy style systems).