Kévin Chalet
Kévin Chalet
`OpenIddict.Core` now references `Portable.BouncyCastle` on `netstandard2.0`, which was necessary to work around the lack of PBKDF2 w/ SHA256 and SHA512 support on `netstandard2.0`-only platforms (which includes .NET Framework 4.6.1, 4.6.2,...
Related to https://github.com/openiddict/openiddict-core/issues/1251. Note: this is also one of the blocks needed for dynamic client registration.
https://openid.net/specs/openid-connect-core-1_0.html#JWTRequests https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-34
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication Note: this includes supporting assertions in the validation stack (for introspection).
The OAuth 2.0 token exchange specification - originally known as "OAuth 2.0 Token Exchange: an STS for the REST of us" - was finally standardized last year. Note: OpenIddict 3.0...
https://docs.microsoft.com/en-us/dotnet/core/deploying/trimming/prepare-libraries-for-trimming
Earlier today, [the first OpenIddict 4.0 preview was pushed to NuGet.org](https://kevinchalet.com/2022/06/22/openiddict-4-0-preview1-is-out/). As part of this release, a new client stack was introduced alongside an `OpenIddict.Client.WebIntegration` package that aims at offering...
The Untappd provider uses GET requests and sends the token request parameters in both the query string and the request form using formurl-encoding, which is a strong sign something is...
AFAICT, `LineAuthenticationHandler.ExchangeCodeAsync()` doesn't seem to do anything special so it's probably not necessary. https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers/blob/cbbc7a1cb78ff9898b6110e8c60aae967fd86356/src/AspNet.Security.OAuth.Line/LineAuthenticationHandler.cs#L35-L66
Hey, To make our lives more painful than they are, some SendGrid APIs - like global suppressions - use `Link` response headers instead of their usual `_metadata` node to expose...