none
SQL MA's objects are getting as explicit disconnectors after deprovisioning RRS feed

  • Question

  • Hi ,

    I have an SQL MA with deprovisoning options as Stage a delete on the object for the next export run.

    I am achieving this deprovisioning by sync rule and not by object deletion rule. 

    Below is the scenario that I did so far...

    I have projected the disconnected objects from the SQL MA's Connected Space manually. I have made this objects to transition into a set manually and then transition out from a set by which the objects can be removed from MV and conncected data source with the help of the deprovisioning options enabled in sync rule and the MA.

    As mentioned above I have selected the option Stage a delete on the object for the next export run and when i run the next export run the object is getting deleted from the MV and connected data source but it is getting as explicit disconnectors in SQL MA's connector space, but I want it to be removed from there as well. Kindly assist me.


    Rajesh Kumar NSR, FIM administrator, Wipro Technologies. India.



    • Edited by Rajesh.NSR Wednesday, March 15, 2017 2:38 AM
    Wednesday, March 15, 2017 2:36 AM

Answers

  • Hi Nosh,

    I have configured a FI_LOGS run profile and ran it...now the explicitly disconnected objects have been removed.

    Can you explain what is the difference between the FI and FI_LOGS?


    Rajesh Kumar NSR, FIM administrator, Wipro Technologies. India.



    • Edited by Rajesh.NSR Saturday, March 18, 2017 7:56 AM
    • Marked as answer by Rajesh.NSR Saturday, March 18, 2017 7:59 AM
    Saturday, March 18, 2017 7:56 AM

All replies

  • I am not sure I totally understand this, but it seems a design mayhem.  I would not do any of this stuff.

    Maybe you need to consider your design options and stay away from manual join. Why are you not doing the set Can you give a little more context in terms of the use case. What are the goals here? What is forcing you to do manual joins of already deprovisioned accounts?   How about creating a second MA to that SQL which will substitute your manual join?


    Nosh Mernacaj, Identity Management Specialist

    Wednesday, March 15, 2017 12:51 PM
  • I want the Metaverse objects that my SQL ma contributed should be deleted.

    It should be deleted both in Metaverse and connected data source.

    I have selected the deprovisioning options in SQL MA as "Stage a delete on next export run".

    I ran export and it has been deleted successfully in Metaverse and connected data source but 

    in the SQL MA's connecter space it is still present as an explicit disconnecter.

    I want it to be removed from there as well...


    Rajesh Kumar NSR, FIM administrator, Wipro Technologies. India.

    Wednesday, March 15, 2017 5:16 PM
  • Any chance you can show some screen shots?


    Nosh Mernacaj, Identity Management Specialist

    Wednesday, March 15, 2017 5:22 PM
  • Hi Nosh,

    I have configured a FI_LOGS run profile and ran it...now the explicitly disconnected objects have been removed.

    Can you explain what is the difference between the FI and FI_LOGS?


    Rajesh Kumar NSR, FIM administrator, Wipro Technologies. India.



    • Edited by Rajesh.NSR Saturday, March 18, 2017 7:56 AM
    • Marked as answer by Rajesh.NSR Saturday, March 18, 2017 7:59 AM
    Saturday, March 18, 2017 7:56 AM