Kévin Chalet

> What is important is that the microsoft identity library is able to exchange that identity token for an access token against the Microsoft Entra application, thereby establishing authenticating client....

> The only real motivation I can offer is that Workload Identities (as they are known on Azure and GCP) and IAM Roles for Service Accounts (as they are known...

> `private_key_jwt` client authentication is something the OpenIddict client itself already fully supports but it is not (yet) easily configurable via `OpenIddictClientWebIntegrationBuilder.Microsoft`, that only offers to register a client secret...

Interestingly, it works if I leave the `Allow manual adjustment of DHCPv6 and Router Advertisements` box unchecked (both the global and the local prefixes announced via ICMPv6 are attached and...

> Interestingly, it works if I leave the `Allow manual adjustment of DHCPv6 and Router Advertisements` box unchecked (both the global and the local prefixes announced via ICMPv6 are attached...

Woooo, very nice @Monviech, thanks for letting me know! 👏🏻 Your post says that `it is best not to use "Allow manual adjustement of DHCPv6 and Router Advertisements"` but did...

> Can you please revisit this PR and provide an update thoughts if we should or not proceed with this PR? I have no strong objection: the lack of reactions...

If we want to make that configurable, the URI will need to be server-controlled (we can't use `post_logout_redirect_uri` for that). @gvkries are you still interested in fixing that?

> If @kevinchalet wants to implement the abstraction on EF or any other store/server (I am pointing fingers because he has done things similar by the past) then it wouldn't...

Hey, > Since OpenIddict fundamentally uses the AspNet identity classes, and extends them with entities such as Appplication, Token etc. we hoped that this would be simple to do (even...