Multiple endpoint single aggregation

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

Version 8.3

Share all details related to your problem, including any error messages you may have received.

So I have been still experimenting with multiple endpoint aggregation and notice that “multiple independent endpoint aggregation” will run each endpoint until it encounters an account and “multiple chained endpoint aggregation” will run until it WON’T find an account. But the question is. Is there a way to have single aggregation run for each endpoint existing in application definition no matter if one endpoint returns value and one does not? (It’s a system that for each endpoint can contain an account that is independent but is an account for the same identity, and we want to avoid excessive number of applications for this system). I already have this figured out for full aggregation of accounts, but the problem seems to be different in single aggregation. Any ideas?

2

I am not clear about your requirement …But in customization rule, you can see the option for single account aggregation.

3

@pradeept
What do you mean? Customization rule runs once the account has been aggregated through endpoint. It basically verifies if the account returned by the endpoint is valid for aggregation and can modify it and either accept it or reject it (or can i do something else with it?). I need that for each “Get Object” operation defined in application aggregation will run with same parameter.

4

Hi @blazejbadzio,

The use-case is to run multiple endpoints until one of them will give account details.

If the above mentioned is the use-case, then we can use after-operation rule and call multiple endpoints until account data is returned.

Let me know if there is some gap in the understanding or your use-case is different.

Thanks

5

There is operation called “Get-Object” you can use it for single account aggregation, just define endpoints in the way you need.

6

@ashutosh08
Thank You. I was wondering how could this be done and i encountered this post
and i tried doing the WebServicesClient config and execute in After Operation rule but that gave me 400 bad request (when I provided everything that was required for the request) i also tried with provided with the operation rule restClient variable and also got same result :confused:

@kjakubiak thanks, but that’s not the case of “simple” webservice connector config

7

Hi @blazejbadzio,

Is it possible for you to share your sample post request and rule xml by removing sensitive details. It would help to look into the issue and then accordingly suggest solution.

Thanks

8

I now figured out that when using the provided earlier WebServicesClient example i got a bad request because the list of allowed values contained 2** and i received an error which said Unsupported token because the WebServicesClient got encoding of empty spaces in url as “+” which is unsupported by application i am trying to connect.
I tried switching empty spaces to %20 but the issue persists.

Post Request would look like this:
{
“Parameters”: [
{
“Name”: “UniqueIdentifier”,
“Value”: “aaa1111”
},
{
“Name”: “DisplayName”,
“Value”: “Name, LastName”
},
{
“Name”: “UniqueIdentifier2”,
“Value”: “long-string-consisting-of-mixed-chars-and-digits”
},
{
“Name”: “EmailAddress”,
“Value”: “[email protected]”
},
{
“Name”:“RequestedApplicationPerrmisions”,
“Value”:“OneFrom(Read,Write,Admin)”
}
]

}

9

Hi @blazejbadzio,

It’s good that the issue is resolved, please mark it closed for others reference for later.

Thanks

10

Issue resolved, I used sailpoint.connectorDependencies.WebServicesClient class to executeGet endpoint. Otherwise it would not succeed. Also the URL had to be % encoded. (Some characters had to be changed to their % notation)

11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.