Support for accepting encrypted OIDC access tokens #47319
Description
Description
Quarkus OIDC can already accept encrypted inner-signed ID tokens but in some contexts such as MCP authorization collocated RS and OIDC provider case, encrypted bearer access tokens may also have to be accepted.
Implementation ideas
Possibly reuse quarkus.oidc.token.decryption-key-location and also add quarkus.oidc.token.decryption-key for letting users inline them, as it is reasonable to expect, when the token encryption is required, the OIDC provider uses the same encryption key for encrypting either ID or access tokens or both.