This may be my understanding of the product, and any help would be greatly appreciated. I have read everything I can find but still having a hard time understanding what is going on here.
Overview
I am working on a PowerShell MA that exports group info to a rest api. This includes multiple owners and some other custom attributes (like category = type of group based on criteria, approvalType = single owner, multiple owner, manager). I have most of
it working and on the home stretch, (I think).
The problem I am facing is on my provision, when I create a new group in ad. I import it then sync the AD MA, I get “The DN must be set before calling CSEntry.CommitNewConnector.”
Info
-The anchor for the MA is a unic sid in the remote system.
-The Join rule is u_objectsid = csObjectID (this is a custom files in the remote system where I want to add the csobjectid on provision.
-Sync rule
Outbound
To all metaverse resources of this type
Scope is group
Scope filter (I have tried a few things here) csObjectid not equal “” (thought was that it would not try to provision until it had this value populated.
Relationship Create resource in external system
Outbound flow ( I have tried a lot of stuff here)
Initial flow = csObjectID =>DN
-My theory on how this SHOULD work.
- The record is imported from ad but no provisioning should happen on my custom MA.
- The record gets provision in MIM and get a csObjectID.
- On export from mim a provisioning gets triggered for custom MA.
- Custom ma export provisions new record in remote system
-what is happening
AD MA is triggering provisioning on custom MA on sync when no csObjectID is in Metaverse.
I was going to try to change the DN but I want to use a value that does not change, I was going to change it to AD objectGuid but that needs to be converted from binary to string which does not seem to happen on initial import/sync and I get the
same result.
Thank you for any help or pointers.
Mike