Support Identity Team With API Calls

[JamieB-gu]

No description provided.

[CDicksonG]

Ashish is currently looking into this for us

[SiAdcock]

This is blocked because the old identity API (pre-Okta, using cookies) still gets hit from pages with pressed interactives. We need to form a plan for pressed interactives going forward as pressing unsupported interactives forever not a sustainable solution.

[shesah]

@ashishpuliyel any updates on this card? can we help?

[shesah]

@SiAdcock to speak to Paul r in I&T to understand what that team needs and then Calvin to speak to Jonathan H on how we address older interactives

[SiAdcock]

From @pvighi:

I noticed that in DCR there still a flag that you can set to not use Okta. I'm not sure if changing this setting will already break anything but I have a PR ready to go that would make some calls not work unless the flag is set to use Okta.
is it a problem with you if we move on with the migration and basically force DCR to have the flag set to Okta, or do you normally remove configuration options before they become "dangerous" ?
To be honest, I'm not sure that changing the Okta flag would not already break anything

[SiAdcock]

Closing in favour of #13020