Kévin Chalet

Looks like no one is interested. Closing 😄

I added a Mixcloud integration to the new OpenIddict client (https://github.com/openiddict/openiddict-core/pull/1594) and I can confirm the `state` issue hasn't been fixed and that a workaround is still needed. (oh, and...

Closing for now. If Mixcloud fixes/improves their implementation in the future, we'll revisit that.

OpenIddict's server offers an opt-in authorization request caching feature that stores the actual payload as an encrypted JWT in a distributed cache and redirects the user agent to the authorization...

> @kevinchalet You want to be able to obtain each property in the token as a JsonElement, to put them somewhere. Do you still the token deserialized? Actually, for this...

Note: if it's too complicated or isn't a good fit for the new serialization model, it's not a huge deal, re-parsing the JWT payload is not the most efficient thing,...

> @kevinchalet if you had a callback that had the utf8bytes, would you be able to use that? Interesting, what would it look like concretely? If you have something ready...

Thanks for fixing that 👍🏻 That said, I'm not so sure it's the best approach: - You're adding yet another mapping (one already exists in `SymmetricSignatureProvider` for the same exact...

Note: this scenario is already possible/supported using something like this: ```csharp if (token.TryGetPayloadValue("claim", out JsonElement element) && element.Deserialize(jsonTypeInfo)) { // ... } ```

> @kevinchalet we currently only keep the JsonElement when we hit a JsonArray or JsonObject, all others are deserialized into C# types. Wait, really, @brentschmaltz? That sounds like a weird...