Update JWT sample code for subscriptions #1171
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous sample handler decoded the parsed JWT token directly using
JwtSecurityTokenHandler
. This works fine when theTokenValidationParameters
were all configured (including the security keys). However, when using OIDC, theTokenValidationParameters
should be generated from theConfigurationManager
, as it needs to download the keys from the OIDC endpoint before theTokenValidationParameter
instance contains the keys. The revised code now is a copy (without much of the event and error handling) of theJwtBearerHandler
logic, so that validation will work similarly to however it is configured within ASP.NET Core. Events are still not implemented at this time.Keep in mind that while this code can be used as a guide for to how to write authorization logic for subscriptions, it is the user's responsibility to ensure that their endpoint is secure. Perhaps in the future we may publish this code in a NuGet package, but for now it is still sample code.