Non-namespaced custom claims deprecation info is unclear

[tyf]

Hi there @clandestine!

@clandestine

It is unclear to me what is required to be done by 1/30/2023 and what is already happening as of 7/28/2022. Can you clarify?

On 1/30/23 the option to allow custom non-namespaced claims will no longer be available - That is, custom non-namespaced claims will be allowed in all tenants. The new restrictions along with tenants that have rules/actions adding non-namespaced custom claims that currently aren’t added to tokens (haven’t toggled off the setting) will introduce breaking changes when all tenants are moved over to the new behavior. This is the main concern and reason for deprecation language.

On 7/28/2022 the toggle to enforce that custom claims must be namespaced was introduced, and thus the ability to allow custom non-namespaced claims as well. By default, I believe this is toggled “on” for all tenants.

@clandestine

Is the addition of this non-namespaced claim going to be deprecated or will it continue to be allowed?

This claim will continue to be allowed - I agree that the messaging is a bit confusing here.

@clandestine

That says that custom claims MUST be namespaced. I don’t see an exception there. Should I expect the behavior suggested in the Custom Claims Migration doc or the text under that button?

Overall, it’s easiest to think about this as toggled “on” as legacy no custom namespace behavior, and toggled “off” as the new behavior which will be enforced by default come 1/30/2023.

Great questions and I hope this helps to clarify!