Hi all,
I'm trying to Collect Identities using a "REST Web Service" Node in a fulfillment workflow but it does not work.
Node settings are shown below:
During the execution, no error is reported but no collection starts. The same issue happens for an Account Collection.
Does anyone know how can i solve this issue? Maybe there's something wrong with the configuration settings?
Version used: 7.0.1 P02
Thanks in advance
Diana
Hi Pooja,
I tried using Response Type:Properties (as you can see in the image) with both:
1. No response variables. In this case Custom Task terminates in Completed State, but no collection really starts
2. Two Response Variable, RUNID and RUNSOURCE, as Web Service documentation reports that collectIdentity call returns this two parameters. In this case, Custom Task terminates with Error. Anyway, i'm not sure about Response variables configuration.
I tried also using Response Type: XML, with both configuration mentioned above but:
1. If i set no response variables, it returns Error.
2. I don't know how to configure any Response Variable setting because system ask me 4 parameters: Variable Name, variable Scope, Expression Type, Expression Pattern
Anyway, Response Type:Properties with two response variable (RUNID and RUNSOURCE) seems to be the proper configuration for this use case. Logs report:
I think the exception refers to the "Collector friendly name", while it's not a required field for the call. ('If no name is provided all collector are proceessed'). Anyway the same exception shows up also if i insert the name parameter in the request URL.
Might be similar to what was discussed in the following post - Workflow REST node: unable to make it work
As Frank suggested, try setting the header variable by the name of "Content-Type" and give it the value of "application/xml"
Hi Boris,
I already did but without success.
In my findings i found that, probably, this is an issue related to the VLG version i use. In fact, in the "RSA® Identity Governance and Lifecycle V7.0.1 Patch 3 Release Notes", this fixed issue is mentioned :
I suppose this is exactly the issue i experienced. As an additional test, i created the same REST Web Service Node (with same settings i mentioned in the first post) in a previous VLG version (v7.0.0) and it works!
I'm pretty sure that the fix you mentioned above (ACM-65328) is different from the issue you are experiencing now.
I suggest you raise a support case.
Mean while, consider the following approach as a workaround - How to run an account data collector from workflow
Hi Boris,
thanks for your answer. I already contacted RSA support.
The approach you suggest (use a subprocess to call a custom task that performs a collection) works for an Identity Collection (the custom task uses a "Collect Identity" Node), though it's not desired solution.
Thanks you
Parsing the return variables is also something that I couldn't get to work in 7.0.1 and 7.0.2. I haven't investigated further but I think this is also a bug and I haven't found a workaround yet (try to fetch the security token from loginUser).
I too tried with response variable but I keep getting Parsing error, but
the message is not detailed enough to know what is it expecting or if the I
need to pass the variables differently.
If this approach has worked for someone on 7.0.1 please share examples. As
a workaround I am using custom task to call ADCs but it does not give a lot
of control in terms of checking the response etc or calling it for a
specific user.
If someone can share the example which worked with Webservice call it would
be helpful
Hi team,
Has anyone tried and is successful in collecting accounts/entitlements for specific user/account using webservice from workflows?
Thanks!
hi,
you can trigger a whole account collection, sure.
Do you want to only update the info for one particular account? what is the surrounding use-case?
Frank
We collect all types of objects using REST/JSON or REST/XML, but not from workflows. We are using a separate system (Securience Data Manager) for the REST collection and the collect from that.
We are looking to do this as well.
In testing with SoapUI, we learned that we can call the IDC webservice without a token if we added the source IP under the trusted IP list - Admin > Web Services > List of IPs allowed to invoke web services:
I am hoping by adding the IP address of the server will allow the IDC webservice from the workflow.
Hi Diane, Are you setting some variables for response?