POST /api/user/invite

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

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

2

Hello Colin, is there any news in regards to this replacement?

Best Regards,

Cian

3

The replacement is still in progress. I will update this topic once the replacement details are available.

4

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

5

Hello @colin_mckibben,

To utilize this, my understanding is that you need the short id of the user. The only way I have found to obtain this is through this API: /cc/api/user/list and the replacement of /user/list doesn’t seem to give that value.

Are there any alternatives to obtain that value to continue using this API once the /user/list is removed? If not, is it possible to extend the use of the /user/list until a proper replacement for the /user/invite has been made available?

Thanks, Braden

6

GET /api/user/list has been extended to June 14th since it is needed by /api/user/invite.

1 Like
7

the short id of the user is also used by /api/app/create if you want to assign an owner to an application

8

I’ve been told that /api/app/update allows you to use the long ID of a user to assign an owner. Can you please confirm?

9

Due to lack of documentation I had to try several things. The Get application API lists owners as:

"owner": {
        "id": "7_digit_number",
        "name": "Angelo Mekenkamp",
        "ownerExternalId": "32_digit_number"
    },

So I tried to update the owner by passing the same information in the body, but by updating the ownerExternalId and by ignoring/removing/nullify the id attribute, which all failed. Also putting the 32 bit number in place of the id failed.

At the end the solution is to drag ownerExternalId outside of the owner object and thus have a body that looks like this:

{
    "description": "new description",
    "ownerExternalId": "32_digit_id_of_new_owner"
}

And it looks like the /api/app/create API does not allow to set the owner and it is set automatically and chooses the identity belonging to the PAT that was used for the API call. I hope that the replacement API will allow setting all attributes during creation, so that it is consistent to other beta/v3 APIs.

But from my end I now don’t see a dependency on the short id of the user for applications. Thank you for your response!

Kind regards, Angelo

1 Like