Add request id in SCIM 2.0 connector paylod

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

[Replace this text with your version of IIQ. The more specific you can be (7.1, 8.3, 8.X), the more people can help. If you do not know, put Unsure.]

Please share any images or screenshots, if relevant.

[Please insert images here, otherwise delete this section]

Please share any other relevant files that may be required (for example, logs).

[Please insert files here, otherwise delete this section]

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

Pradeep Kumar5:36 pm

Hello everyone
We want to add request id in payload. How can we do this. can anyone help please.

Thanks

2

Can you please share how you need it in payload?

3

Hi @sukarande , Here is the desired payload
Update Account JSON using PATCH : {“schemas”:[“urn:ietf:params:scim:api:messages:2.0:PatchOp”],“requestId”:“0000385257”,“Operations”:[{“op”:“add”,“path”:“groups”,“value”:[{“value”:“150449”}]}]}

Thanks

4

@pradeep_kumar54 As it a SCIM connector, I don’t think you’ll have flexibility to modify the request payload. You might need to refer the documentation or coordinate with sailpoint support.

As an alternative, you can use webservice connector, which gives you control over the payload to add more attribute or add some default attribute, etc using Before Rules.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

5

Thanks @neel193 , let me check.

6

@pradeep_kumar54 You can also try setting it up using Before Provisioning rule, in case it works. If it’s not, best bet would be to switch to WebServices connector.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

7

Hi @neel193 , @sukarande ,

Updated the before provisioning plan, I am able to add requestId”:“0000385257” in the payload during create operation. But it is not added during modify operation. Any idea why?

Thanks

8

@pradeep_kumar54 Could you please share your before provisioning rule and sample logs printing plan before and after adding the request id.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

9

Hi @pradeep_kumar54 , From where are you calling this SCIM API?

Thanks,

PVR.

10

Hi @Peddapolu , its a SCIM 2.0 connector app we are using.

11

Hi @pradeep_kumar54,

Since the SCIM 2.0 connector is already confirmed, you can proceed with updating the provisioning policy. Add the required attribute and map it to the requestId value extracted from the ProvisioningProject object. Once the mapping is in place, the connector will return that value during provisioning. Make sure to add the same attribute to both the application schema and the SCIM configuration object so the system recognizes and updates it consistently across all layers. you can use existing attrubite externalId too.

Note: If you are calling outside of the SCIM connector, it will also work with external attributes.

image
image1868Ă—582 41.8 KB

I hope it would work!.

Thanks,

PVR.