Windows Local Connector Provisioning

[ashishbhatia_custih (Ashish Bhatia)]

Hi,

We are deploying provisioning policy from Sandbox to Production for Windows Local Connector, Policy works as expected in Sandbox but not in Production and we are unable to create account in Production.

We have below provisioning policy in Connector.

{
    "name": "Account",
    "description": null,
    "usageType": "CREATE",
    "fields": [
        {
            "name": "sAMAccountName",
            "transform": {
                "type": "rule",
                "attributes": {
                    "name": "Create Unique Account ID"
                }
            },
            "attributes": {
                "template": "$(hostName)\\$(uid)",
                "cloudMaxUniqueChecks": "50",
                "cloudRequired": "true"
            },
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        }..
..
..... other attributes
    ]
}

In Sandbox, $(hostName) gets replaced with hostname of the server say, SABIAM01 and we get below value

SABIAM01\ashish

but same doesn’t works in production, and we only get
\ashish

we have Disable Qualifying Local Objects as unchecked.

[KRM7 (Krishna Mummadi)]

I believe you have Identity attribute hostname, check that mapping and transform if any. Looks like hostname attribute is empty for whatever user you are testing.

[ashishbhatia_custih (Ashish Bhatia)]

Hi Krishna,

No, we don’t have any attribute like that. Moreover I deployed the same policy for multiple windows sources and it replaces the hostname at run time in Sandbox, but same didn’t work in Production.

[KRM7 (Krishna Mummadi)]

How do you get the hostname, somewhere it has to be defined rite.

[ashishbhatia_custih (Ashish Bhatia)]

So, as per document we have hostName in samAccount if Disable Qualifying Local Objects is unchecked, which is our case it is.

Moreover, we never defined in our sandbox, then how is it working?