Hi all,
We are facing a scenario where we need to disable application accounts using Batch requests. After running batch request, the account does not seem to be disabled
Is it possible to disable an application account with Batch requests for whom disable operation is not defined?
Thanks in advance
Yes, you can perform account disable using batch process. Sample csv data is as below. Instead of EnableAccount, use DisableAccount
@Arpitha1 When I run the batch request, it does not disable the application account. Is it possible because the disable operation is not defined on the application? Or does it not depend on the operation definition on the application
@rishavghoshacc which connector is it ?
Hi @rishavghoshacc ,
What is the current status of the batch request you executed?
Is the status “executed” and the application account not disabled?
Did you try to disable the application account from Manage account?
@Arun-Kumar The batch request shows executed but the account is still active in IIQ. Also tried the disable option in manage account. It says that the disable is complete but the account still remains active
Hi @rishavghoshacc ,
If it is a web service connector, you need to specify the HTTP operation(disblae account) for disabling the account.
Did you review the Access Request created for disable account using batch request or the Manage Account section?
@Arun-Kumar What about JDBC and Delimited applications? Does the operation need to be defined there as well?
Hi @rishavghoshacc ,
For JDBC connectors, you need to define the logic for disabling an account in either the Disable Provisioning Rule or the Global Provisioning Rule.
DelimitedFile Connector does not support direct provisioning. By default, any provisioning operations for DelimitedFile applications will trigger a Manual WorkItem.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
