Anchor/DN for a custom MA ------ But the anchor will be unknown until after the MA has provisioned.... RRS feed

  • Question

  • Hi all.
    I've been working on a custom MA (ECMA2) and altering it (it was created by someone else a few years ago).

    At the moment the anchor used is the samaccountname. Which doesn't normally change, but when it does the MV creates a new instance of that MA etc (as it should, I just remove the old entry after a full import).

    I'm wondering if I can change this anchor to use an unique attribute... The only issue is that that attribute (MSID) will not be known (in the MV) until after the CS has been created on the external system.

    From my understanding this is how the prebuild MAs work, for example the AD/LDAP MA uses the AD DN as a mapping but it's really linking to the SID/GUID under the hood..

    Any tips/directions/additional questions?

    Friday, March 31, 2017 2:01 PM


All replies