Hi all,
I have a web services SaaS source, where I get an account attribute status which can have values Active and Disabled. In the UI → source → edit configuration → Connection settings, there is an attribute called Account Enable Status Attribute. This field (and others) is not documented in the corresponding connector documentation.
If left empty, the field suggests status = Active (with spaces around the equality sign). The instructions next to it suggest status=Active (without spaces around the equality sign). I tried out both and noticed that this is giving a different behavior. This is not user friendly and also not matching to the regular Web Services connector. Both options are not completely working, but I noticed it comes closest when having status=Active without spaces.
Also I noticed that the UI value for status is not always matching the expectations. Upon closer inspection in the json object of the account when fetching it through GET /v3/accounts/id, I noticed the account attributes have two values on top of the account attributes that we have defined. They are IIQDisabled and IIQLocked, which I have seen sometimes for sources from other connectors as well. However, if one tries to enable an account that was disabled, the value IIQDisabled disappears and the attribute disabled wait value true appears in the account attributes (and thus not only outside of the attributes array). As a consequence, the UI gives the wrong value for status. (I think the UI should both show the value for the account attribute status as known in the account schema, as the value calculated from status=Active, AKA, the IIQDisabled value.
I think another round of testing should be done by SailPoint on this connector. As it does not seem to behave correctly.
Kind regards,
Angelo