AD Account Creation in a disabled state

Identity Security Cloud (ISC) ISC Discussion and Questions
,
10

We were still having issues.

used some logic like the below example.


                {
                    "eventActions": [
                        {
                            "Action": "UpdateAttribute",
                            "Attribute": "carLicense",
                            "Value": "#{now.EPOCH_TIME_WIN32}"
                        },
                        {
                            "Action": "ADMoveAccount",
                            "Attribute": "AC_NewParent",
                            "Value": "#{identity.adou}"
                        }
                    ],
                    "Identity Attribute Triggers": [
                        {
                            "Attribute": "cloudLifecycleState",
                            "Value": "active",
                            "Operation": "eq"
                        }
                    ],
                    "Account Attribute Update Triggers": [
                        {
                            "Attribute": "carLicense",
                            "Value": "*",
                            "Operation": "eq"
                        }
                    ],
                    "Operation": "Modify"
                },
{
                    "eventActions": [
                        {
                            "Action": "UpdateAttribute",
                            "Attribute": "carLicense",
                            "Value": "#{now.EPOCH_TIME_WIN32}"
                        },
                        {
                            "Action": "ADMoveAccount",
                            "Attribute": "AC_NewParent",
                            "Value": "#{identity.adou}"
                        },
                        {
                            "Action": "ChangeOperation",
                            "Attribute": null,
                            "Value": "Enable"
                        }
                    ],
                    "Identity Attribute Triggers": [
                        {
                            "Attribute": "cloudLifecycleState",
                            "Value": "active",
                            "Operation": "eq"
                        }
                    ],
                    "Account Attribute Update Triggers": [
                        {
                            "Attribute": "roomNumber",
                            "Value": "*",
                            "Operation": "eq"
                        }
                    ],
                    "Operation": "Modify"
                }

I believe this helped some timing issues with other event lifecycles.

Is this common? Shouldn’t the connector detect a move event and hold other operations until it is completed?