Does the Oracle DB Connector support deleting an account?

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

Hello Experts,

I have gone through the Oracle DB connector document, I can see the connector features shows that it can enable/disable accounts.

My client wants it to be deleted, is it possible? Any ideas?

FYI*

I do not have workflows in my tenant.

I do not see any after operation rule for oracle db.

Regards,

Shekhar Das

2

Not an expert, though. Just my two cents.

Out of the box, the Oracle DB connector doesn’t really do hard deletes; it’s mostly enabled/disabled by updating a status column.

If your client wants actual row deletion, that’s not supported directly.

You’d need a custom approach (like SQL via Web Service or a rule).

Since you don’t have workflows/rules in your tenant, you’re limited here.

The best practical option is to treat the disabled as deleted.

3

Hi Shekar,
You should be able to use delete operation by modifing provisioning plan from disable to delete on operation request. (Use before provisioning rule)

accountRequest.setOp( ProvisioningPlan.ObjectOperation.Delete);

Second option, is configure a new JDBC connector for Extend account delete behaviour.

Thanks

4

@iamkiran Thanks for your response.

Yes, it doesn’t do the deletion. I was looking for any other approach if anyone have experience with this use case.

I am not sure how we would do with webservice because webservice connectors are meant for API’s.

I am not sure which rule you are referring.

Regards,

Shekhar Das

5

@raghav_chouda Thanks for your response.

Hope you are aware of new feature to invoke delete operation from ID Profile.

Anyways if you use a BP rule or invoke delete from ID Profile it is only going to remove the account from ISC not from the target as the connector itself doesn’t support delete operation.

With regards to JDBC connector that I definitely believe an option here. But need to do some feasibility check.

Regards,

Shekhar Das

6

Hi @shekhardas1825 - you might talk to the DBA and see if they can create a stored procedure you can call as part of the disable that will execute a delete on the DB side. I have seen that used before.