Clientmetadata is not having any information under access requests pending approvals API

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

As per the document provided under list-pending-approvals | SailPoint Developer Community , we will have clientmetadata, however we don’t see any value under this when we run the API from postman. Needs Inputs on this

2

Hi @bkumar592,

Do you add a client metadata when submit your access request ?

As is describe here : create-access-request | SailPoint Developer Community

image
image831×192 10.2 KB

clientMetadata is just a key-value pair that you can add arbitratry when you submit your request. This can only do if you use api for submit access request not from request center.

What are exactly your need about this clientMetadata ?

3

Thanks for the response @baoussounda .
If my understanding is correct if we submit a request from request center and verify details from API we don’t see clientmetadata.
What are exactly your need about this clientMetadata ?
we are trying to get the Source Name from the request. Also, I have verified that we don’t have any information in the request regarding the source name.
Thanks in Advance for the help!

4

Hi @bkumar592,

Yes exactly, because clientmetada is an arbitrary key-value pair that you can add into your request when you submit request via api. But from request center you not have a possibility to add any information in client medata. And if you check by api request that was submitted from request center its normal that to have a null clientmetadata.

“We are trying to get the Source Name from the request. Also, I have verified that we don’t have any information in the request regarding the source name.” ==> for this need you can do it with script. you can retreive list of access requests, for each reques you have “type” : “ACCESS_PROFILE”, “ROLE”, or “ENTITLEMENT” based on type of access you can use an appropriate api to retrieve this access details and you will find source information on this access details.

5

Thanks for the clarification @baoussounda , earlier we used to see appName value for the request and we take it forward from there. Is this is a change happened due to API deprecation?

6

Hi @bkumar592 ,

in my side a never see this information (appName) into the request. in what object key you see ealier this information ?

7

Hi @bkumar592,

The clientmetadata populates only while submitting the Application request (not for Entitlements or Access Profiles) from the request center.

It will show something as below :

"clientMetadata": {
            "requestedAppIcon": "https://files.accessiq.sailpoint.com/modules/builds/static-assets/perpetual/identitynow/icons/2.0/default/",
            "requestedAppName": "Test",
            "requestedAppId": "885a3bf061544bc781d741994887b956"
        },

Are you looking at an application request.?

8

Hi @jesvin90 , Based on the list of access requests we have created a script based on the clientMetadata where we checking for requestedAppName attribute value.
Do we know, what type of request it is like application, access profile, role, entitlement from the request.
Thanks
Narendra

9

Hi @bkumar592,

As far as I have tested it, clientmetada populates only for Application requests, unless specified through an API call for other type of requests.

The above response is for an Application request and it gives only the application details, NOT the source details.

10

Hi @jesvin90 , thanks for the clarification, I don’t think we have an attribute which can help us about the source name.
Thanks
Narendra

11

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