How to link Access profile in Application (bulk)

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

Hi, I’m having a problem, I have load around 523 access profile using Visual Studio.

my problem Start when I want to pick the access profile that I have created into the application that created. I can only see up to 250 access profile. I’m still missing 273 APs that need to be link to the application. we have 800 limits, and I know Ui have a limitation of showing only up to 250 APs, so how can I add these remaining AP into the application. I have tried to use patch/post, but it didn’t seem I can use an API call for these as i get a 404 error.

I found we can use a private call /cc/ but I saw in the post it might have been deprecated. So, my question is, how can I increase the limit in the UI? or is there is any way I can do this safely.

Thank You.

2

@wawa You can use Offset in query parameter to view the next 250 records through API.

3

Hi @wawa

It seems like there a new endpoint for apps patch-source-app-v-1 | SailPoint Developer Community

access profiles can be patched.

Thanks

4

Hi,

You can handle this by using pagination with offset in the v2026 API.

GET /v2026/access-profiles?limit=250&offset=0

GET /v2026/access-profiles?limit=250&offset=250

GET /v2026/access-profiles?limit=250&offset=500

5

@wawa You cannot increase the 250 AP display limit in the UI — API is the only way

6

Hi Pucha, i have use this before. but I can only see it in the API call result. is there is any way I can change in API the limit, so I can see it here, because this is where I’m stuck. I cannot add the remaining 273, because it won’t show here.

or if there is any patch for application available, so I can add my remaining 273 APs to this dedicated application? Because the one I found is on how to patch the APs, but I don’t want to patch the APs, I need to patch my application, so the correct APs is shown in my application.

image
image1134×406 17.1 KB

Thank you in advance.

7

The offset/pagination suggestions in the replies above are for listing access profiles via the API, but I don’t think that’s your actual problem. You are trying to link access profiles to the application (source app), and the UI caps out at 250, right? If so, try to use the API to add the remaining 273 directly.

The endpoint you want is:

PATCH /beta/source-apps/{sourceAppId}
Content-Type: application/json-patch+json
X-SailPoint-Experimental: true

With a body like this:

[
  { "op": "add", "path": "/accessProfiles/-", "value": "<access-profile-id>" }
]

The /- appends to the existing list, so it won’t overwrite the APs you’ve already linked. You can also batch multiple adds in one call:

[
  { "op": "add", "path": "/accessProfiles/-", "value": "<ap-id-1>" },
  { "op": "add", "path": "/accessProfiles/-", "value": "<ap-id-2>" },
  { "op": "add", "path": "/accessProfiles/-", "value": "<ap-id-3>" }
]

You said you got a 404 error when you tried to use an API call. I think that was probably because the ID you used was the source ID, not the source app ID. Those are different. To find the right one, use the /all endpoint, which returns every source app in the org:

GET /beta/source-apps/all?filters=name eq "YourAppName"
X-SailPoint-Experimental: true

Then use the id from that response in your PATCH call.

As Ousmane N’DIAYE mentioned, there is also a newer v1 version of this endpoint (PATCH /source-apps/v1/{id}) If you want to use that instead, same behavior, also experimental.

For 273 APs, just script a loop through your AP IDs and fire the patch calls. This thread has a working Python SDK example if that helps.

And yeah, skip the /cc/ route. That is deprecated and not something you want to rely on going forward.

8

Thank you. this help a lot. im able to patch it now. :smiley: