Finally a chance to get rid of claim type mappings!

[leastprivilege]

With the 6.x release of the MS JWT handler, the mapping of artisanally crafted, spec-compliant claim types to their WS-* counterparts from the late 90ies is finally gone!

That means you can now get rid of this behavior in your OIDC and JWT handlers for v5! That's great!

I can totally understand that this is a breaking change, and you probably want to keep the wrong behavior by default for a little while. But maybe a simple opt-out switch is now possible?

e.g.

// behave like a claims-based gentleman (defaults to false though)
options.LeaveMyClaimTypesAloneFfs = true;

Alternatively maybe

options.ClaimsActions.Clear();

Also imagine how many backlog issues you can finally close that are related to that problem. It's a win-win.

[damianh]

Kill it with 🔥

[blowdart]

We need to check for breaking changes other than this first.

@Tratcher to guide @JunTaoLuo in evaluating compat of the new version, with @HaoK to make the PR.

[chriskuech]

defaults to false though

Considering how hard it is to bump the major version of .NET in legacy applications, defaulting to false will definitely prevent more headaches than defaulting to true.

[Tratcher]

@HaoK ready to close?

[HaoK]

As long as we aren't planning on doing any additional flags or clearing of defaults?

[Tratcher]

We'll let folks try the nightly or preview and see how disruptive it is for them.

@leastprivilege @damianh @kevinchalet