ISC Authoritative SOurce Delimited File - Disable Account via API

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

Current Setup:

  1. We have an authoritative source configured as Delimited File connector. (We have added ENABLE featureString for enable/disable functionality else the disable account api call was not happening and UI was also not showing disable account)
  2. Accounts are created using https://sailpoint.api.identitynow.com/v2026/accounts api call.
  3. The ISC Identity is created post the account is created.

What we need:

  1. We are trying to disable the account in the authoritative source using disable api : https://sailpoint.api.identitynow.com/v2026/accounts/:id/disable
  2. We are also looking forward to enable and delete account options via api call.

Current situation:

  1. The disable account api call is executed with response as taskID but a manual task is created to complete.
  2. Post completion of the manual task, account is not disabled.
  3. Also manually disabling account via UI is also not working.

Is there any way we can disable the account in authoritative source and eventually mark the identity as inactive.

2

Hello Nihar,

Please try add “ENABLE” feature to the connector configuration. The enable/disable account will be displayed in the UI and the actions will be automatically provisioned.

put-source | SailPoint Developer Community

3

I have already added ENABLE in features attribute of Source

4

UPDATE: We also tried adding an attribute for lifeCycleState and configured the terminated lifecycle state to send disable account for all Source.

It did send the disable account events for IdentityNow source (This got disabled correctly) and for the delimited file auth source, it created a manual task which even after completing still shows the status as enabled.

image
image1092Ă—235 12 KB

5

I had a similar case and what we did was:

  • enable provisioning flag in the source
  • add ENABLE feature to the delimited source
  • configure the delimited source in LCS.
6

Hello Nihar,

Did you check the IIQDisabled account attribute?

For Delimited File accounts, the enabled/disabled status should be driven through IIQDisabled, not the normal Disable Account action. SailPoint documents IIQDisabled as the Boolean attribute used to mark a Delimited File account enabled/disabled in ISC: Delimited File Account Attributes.

image
image2440Ă—496 52.9 KB

IIQDisabled = true   → account disabled
IIQDisabled = false  → account enabled

For API updates, try updating the flat-file account attribute directly with PATCH /v2026/accounts/{id}. SailPoint notes that account attributes can be modified only for flat file accounts: Update Account API.

Also, account status and identity status are separate. For making the identity inactive, use Lifecycle State / cloudLifecycleState mapping: Setting Up Lifecycle States.

This older community thread points to the same IIQDisabled approach: Account Status - IIQDisabled Attribute For Delimited File Source.