GET /api/profile/get

Replaced by GET /v3/identity-profiles/<identity-profile-id>

End of life 31/12/2023

GET /v3/identity-profiles/ offers less functionality than GET /api/profile/get.
v3/identity-profiles/:identity-profile-id/lifecycle-states is replacing another part of the deprecated API, but even that does not cover it in full.
We miss v3 APIs to manage security options on the Identity Profile
See UI, things like invitation options, sign-in method, block access from, password reset and user unlock settings/methods and strong authentication methods and the error message are now missing from the v3 API.

6 Likes

Yes, you are correct. Those specific pieces of functionality are not yet introduced in the v3 APIs. Product is already aware of these gaps and has a plan to implement them in v3 in the coming months. Stay tuned for more updates.

1 Like

Hey Colin is there a timeline on this or is it just Coming Soon™?

Our documentation tool uses these CC APIs to fetch that configuration data that Angelo mentioned (which is being presented at developer days)

Is there any API/workaround to export information from settings page of the Identity profile ?

It appears that quite a few of the settings in the identity profile are using private APIs. I haven’t tried myself, but maybe you can use the SP-config API to export the identity profile and get all of the settings.

From what I can read here @colin_mckibben, The product team was already aware of these gaps and they had a plan to implement these in the then upcoming months (which I assume would be the months in 2023). Can you please check if these plans still exist and are perhaps stuck in a backlog? Are there still plans to have these attributes manageable in a dedicated API endpoint?