POST /api/app/update/{appId}

Identity Security Cloud (ISC) Non-Public API Deprecations
1

This API’s shutoff date has been extended to November 1st.

This API is replaced by the following endpoints:

To add an access profile to an app, use the following endpoint and payload:

PATCH /v2024/source-apps/:id

[
    {
        "op": "add",
        "path": "/accessProfiles/-",
        "value": "52de1e8b6c99493d8d306f749a0716cf"
    }
]

For a full mapping of /api/app replacements, please see this doc

IDN-V2024 Public Preview Apps API mapping from legacy CC endpoints-090924-215538.pdf (595.0 KB)

v2024 experimental endpoints will be available by end of this week. Both beta and v2024 experimental may change with little to no notice. Please see our API versioning strategy for more information.

2

Hi @colin_mckibben. I didn’t see the /cc/api/app/uploadCustomIcons API referenced anywhere in the API deprecations. Is this one being included as part of “update”?

3

bump @colin_mckibben

4

Just created a topic for it here: POST /api/app/uploadCustomIcons

1 Like
5

The access profile enrollment does not happen if there is an identity update going on in the back end. This results in an error message: ((SLPT-1211) Your updates cannot be saved while a related task is running. Please try again later.) and the customer has to wait a long long time just to update one application.

Is it going to be fixed with the new API?

3 Likes
6

Hello all. Will there be a PATCH /api/app/update/{addId} api route available eventually? I’m sure there are other patch uses cases but we have code that associates access profiles with apps and current state you have to go retrieve all the currently associated access profiles, add any new ones, and then make the post call. A patch ability would be great so you could just submit which access profile(s) you’d like to append.

2 Likes
7

+1 on this question. This is a huge pain point for our support teams and our Governance customers. We had to implement a complex process using an AWS queue, AWS Lambda, and some custom message submission tools in order to work around this and it’s still a pinpoint as it can sometimes take up to 24 hours before access profiles can be associated with apps.

8

We are using workato recipe to make calls on interval as it never works with single call.

9

The replacement for this API will be available by the end of June, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to August 30th.

1 Like
10

Is the same api as /cc/api/app/update/
We are trying to migrate all of these over to the newer api’s so I am just double checking.

11

Yes, this is the same the API as you described. The end of life date has been pushed back to august.

12

Hi @colin_mckibben,

Do you have any inputs to share on this replacement ? When will it be available on sandbox environment ?

13

It should be available by the end of this month (June). It won’t be turned off until August.

14

Any chance we can get some answers to some of the other questions in this thread?
(no PATCH verb, and refresh often gets stuck – which blocks API calls)

Is this new v3 version going to address those issues?

15

Hello Colin,

Any news about this new endpoint ? :smile:

Have a good day,
Thomas

1 Like
16

Hi @colin_mckibben, can you please give an update on this one as the API does not seem to be available yet. I can’t find it in the documentation at least.

If the replacement date is indeed postponed, does this mean that the shutoff date will be postponed similarly?

Kind regards,
Angelo

18

Hey @angelo_mekenkamp,

I just heard about the /app endpoints, we will have endpoints available toward the end of July.

This does in-fact push back the shutoff-date to Sept 27th.

2 Likes
20

The replacement for this API will be available by September 3rd. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to November 1st.

1 Like
21

This endpoint doesn’t seem to work anymore or rather seems like it’s expecting a different payload, we’re getting ‘Bad request syntax’ when passing list of access profiles. Any alternatives for assigning access profiles?

22

Can you provide an example of the payload you used and the exact error message you received?