How to Map active/disable account status Using userAccountControl in a web services connector?

Which IIQ version are you inquiring about?

iiq 8.5

Share all details about your problem, including any error messages you may have received.

*I am working with web services connector which configured to connect to Active Directory. I need to map the account status for the web services connector based on the userAccountControl attribute returned by the web service API.

The requirement is:

  • If userAccountControl = 512, the account should be considered Active.
  • If userAccountControl = 514, the account should be considered Inactive/Disabled.

I would like to derive a custom account status attribute from userAccountControl so that the web services connector correctly reflects the Active/Inactive status of the AD accounts in SailPoint IIQ using Build map Rule. But unlike JDBC connector or Delimited File application , the web services connector does not have a “Build Map Rule” option under the Rules tab (connector rules section).*

Hello Rimon. For the Web Services connector, you may not need a Build Map Rule if the API only returns 512 and 514.

I would first make sure userAccountControl is in the Account schema and Account Aggregation response mapping, then try setting Schema Attribute for Account Enable status to:

userAccountControl=512

This should treat 512 as Enabled and 514 as Disabled (General Settings). AD userAccountControl is a bitmask, so enabled accounts are not always 512. The disabled flag is 0x0002.

If other UAC values are possible, I would use an After Operation Rule on Account Aggregation and evaluate that bit:

Map result = new HashMap();

if (processedResponseObject != null) {
    for (Map account : processedResponseObject) {
        Object value = account.get("userAccountControl");

        if (value != null) {
            int uac = (value instanceof Number)
                ? ((Number) value).intValue()
                : Integer.parseInt(value.toString());

            account.put("IIQDisabled", (uac & 0x0002) != 0);
        }
    }

    result.put("data", processedResponseObject);
}

return result;

For the rule-based case, I would set IIQDisabled directly. SailPoint documents that the Web Services connector does not honor the Account enable field when that value is set by an After Operation Rule (Troubleshooting).

After the change, run an account aggregation and verify one enabled and one disabled account.