Identity Security Cloud BP Rule – Recommended Way to Access Attributes from Another Source

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

Hello Lalitha, HTTP 202 only means ISC accepted the request and created an async task. It does not confirm that the account was actually enabled. The first thing I would try is sending an empty JSON body:

{}

For this test, remove both externalVerificationId and forceProvisioning.

There is also a similar community case where the API returned a task ID but the account did not change, and using an empty body resolved it.

image
image1832×946 95.1 KB

If it still does not work, check the returned task/account activity and compare it with the activity generated when enabling the same account from the ISC UI.