none
Ignored flow rule name in AD extension code when running AD full sync RRS feed

  • Question

  • I'm using some rule extensions in AD management agent.

    I get to some problems, when trying to run AD full sync. When I run full sync on other management agent than AD, I get lets say both flow rule name cases. But when I run AD full sync, I get only the first, but somehow I don't get the second flow rule name.
    Maybe someone can help why one flow rule name is ignored on AD full sync?

    My code example from AD extension dll:

    void IMASynchronization.MapAttributesForExport(string flowRuleName, MVEntry mventry, CSEntry csentry) { switch (flowRuleName) { case "case 1 name": //code break; case "case 2 name": //code break;

      default:
                        throw new EntryPointNotImplementedException(); } }



    • Edited by Safary123 Tuesday, October 24, 2017 1:59 PM fix
    Tuesday, October 24, 2017 12:26 PM

All replies

  • I would need to know what is supposed to happen, as supposed to a SUDO code, but one thing I see you are missing the default case.


    Nosh Mernacaj, Identity Management Specialist

    Tuesday, October 24, 2017 1:11 PM
  • I have default case, code works fine, I will correct example.
    The problem is that I want to know why on full sync AD MA, one specific case is not hit, but on other full sync MA it is. Why one specific flow rule name is not given to method MapAttributesForExport() when I only run full sync on AD MA?
    Tuesday, October 24, 2017 1:58 PM
  • And this is the same exact code on both MAs?

    Nosh Mernacaj, Identity Management Specialist

    Tuesday, October 24, 2017 2:02 PM
  • Sorry if I misguided you, but I found now that when I run Full Sync on HR or FIM, then AD extension code, method IMASynchronization.MapAttributesForExport is executed and case 2 is hit.
    But when I run AD Full Sync, method IMASynchronization.MapAttributesForExport is executed and case 2 is not hit. Even though nothing in AD management agent was changed in that time, flow rule names stayed the same.

    Second thing I've found, that in AD MA, attribute flow, when I select case 1, I can add "Allow Nulls" option, but when I select case 2, "Allow Nulls" option is disabled. Case 1 and case 2 even uses the same metaverse attributes.
    Maybe it is skipped, because case 2 attribute is configured like some anchor or something?

    Wednesday, October 25, 2017 10:07 AM
  • This has to do with the way synchronization rules are processed. If during a Full Sync in HR MA something triggers a change to AD, that is when this code will execute.

    But, for a second forget the code and tell me what is the issue in real life. What is not working?


    Nosh Mernacaj, Identity Management Specialist

    Wednesday, October 25, 2017 7:51 PM