400 Error - Disabling Identity

Our team was disabling a single identity from the details tab here:

We ran into the following issue:

This identity does not own any Roles or Access Profiles.
The error message lists all the Access Profiles and Roles in the tenant.

The same issue does not arise when disabling from the Identity list as shown:

Any insights would be greatly appreciated.

Thank you.

1 Like

I too get this same error. The details page is using the /cc/api/user/enabled API to disable an identity, which results in the error with a bunch of items that the identity doesn’t own. If I disable the same identity from the identity list, then it works. The identity list uses the /beta/identities-accounts/{id}/disable API. I think this is a bug and should be reported to the support team. Can you please open a support ticket?

A ticket with Case No CS0223380 has been opened.

4 Likes

Hi @colin_mckibben @atarodia
We are also facing the same issue while we are disabling the identity using cc API from a script. Please let us know once the issue got fixed or else suggest us so that we can also create a case for the same.
Thanks
Narendra

1 Like

If you are using the cc API in a script, then I recommend switching to the beta API. That will fix your issue immediately while also getting you off of the private API.

2 Likes

Hi @bkumar592,

Regarding the ticket, Support has created an engineering ticket and it is being worked on.

1 Like

Hi @colin_mckibben
Thanks for the response and we looking to replace the cc API with beta API. Does this cc API for enable is going to be deprecated and can we consider the beta API as an alternative.
Please let me know your inputs.
Thanks
Narendra

1 Like

It is not yet deprecated, but I suspect this /cc endpoint will be deprecated in the near future. I think you will be better off migrating to the beta endpoint in preparation for a v3 replacement.

1 Like

Received an update from the support that the dev team has started working on the fix. Though, they still don’t have an ETA

1 Like

The issue has been resolved by the engineering team. Thank you everyone!

2 Likes

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