Full Aggregation API Not Working in Workflows

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

Hi all,

I have created one workflow to run the BETA\load-accounts API (for aggregation) on scheduled.

Below are the details:
Authentication: OAuth 2.0
Token URL: https://TENANT.api.identitynow.com/oauth/token
request URL: https://TENANT.api.identitynow.com/beta/sources/SOURCEID/load-accounts
Content-Type: multipart/form-data
Method: POST
Request body: disableOptimization : true

But when I test workflow to run, the workflow keep running at the HTTP action item and will not finish:

image
image657×453 18.3 KB

There is no error return, but the workflow will not end and there is no aggregation triggered at the source.

I tried to run on POSTMAN and there is no issue.

I tried to use same client ID and secret to run other BETA POST API also no issue.

Please kindly advise on this.

2

Hi @sst11 , have you checked execution logs, if yes, what are the details you are getting are you able to see ActivityTask details or HTTP Request step in the execution ?

3

Hi Rakesh,

Yes I have checked the execution log, it shows me 500 error code.

4

Are you tokenizing SOURCEID with {{SOURCEID}} ? If any variables are involved, you need to enclose those variables in {{ }}.

5

Hi Kapil,

No, I actually enter the real source ID in the URL instead of tokenizing it. It is something like this:
(https://tenant.api.identitynow.com/beta/sources/123456789/load-accounts)

6

What is your source Type? It is not possible if it is delimited. Also, did you add Content-Type: multipart/form-data in header inside workflow HTTP Action?

7

Hi Kapil,

My source type is SQL Loader, and yes I added the Content-Type: multipart/form-data in the header section as well.

8

@sst11 can you try the v 2024 api. also when you tried from postman did you try from postman browser one or on premise one ?

9

Hi Shantanu,

I have tried v2024 api, but it will result to Request Failed when I run test workflow.

I tried from postman on prem, not browser one.

Thanks!

10

Hi Shuen,
Have u kept the request content type as the form

image
image352×430 6.14 KB

11

Hi Tulasi,

Yes, I have set it to Form.

image
image442×591 13.2 KB

image
image412×612 16.4 KB

image
image419×609 11.2 KB

image
image408×445 9.46 KB

12

Hi all,

I have figured out the way - it is because the client ID and secret I used is the API I created from the API Management in the tenant.

But according to the another post - Using Workflow's HTTP Request Action to Work With IdentityNow APIs - #6 by colin_mckibben

We must use PAT to call the API. Once I changed to my PAT in the workflow and now the workflow can run without issue.

Thank you everyone for the kind assistance!

2 Likes