[Question] Performance consideration

I am using the JwtSecurityTokenHandler for encoding and decoding/validating JWT. I use the JWT as SET. I have a high load of JWT, and I have some issues with the current implementation of the handler.

First of all, I have to pass by ClaimPrincipal and Claim which are perfect for the usage of JWT as identity, by useless for other usages. As Claims are basically a key/value string pair, I have to convert back to JSON if the value were a JSON content type. (JSON => string => JSON).

The second performance issue seems to be on the Base64UrlEncoder. Encoding produce a lot of string allocations, mainly due to the Split().

Do you plan to enhance the JWT performance, or even to split the packages (IdentityModel feature on one side, JWT management on the other side) ? Am I using the correct library for my usage (a JWT not for the identity) ?

[brentschmaltz]

@ycrumeyrolle I opened the following to add such a feature: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/660

[ycrumeyrolle]

Maybe something like

public virtual JObject/string ValidateToken(string token, TokenValidationParameters validationParameters) { }

?