You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having such a factory will let the users (optionally) integrate with any certified OIDC servers. It will also allow to support the encrypted tokens issued by such servers (which choose to encrypt them) since importing the private keys of these providers into MP-JWT endpoints is not possible.
The text was updated successfully, but these errors were encountered:
Now that we have split the implementation into sub-modules, the solution to this issue becomes clearer:
introduce smallrye-jwt-introspection module which will have
CDI AlternativeJWTCallerPrincipalFactory which will use Mutiny Vert.x WebClient to introspect a token
If the introspected token is active and it is JWT then DefaultJWTTokenPrincipal is returned
if it is not JWT then it is created from the introspection response which may include the username and a few other properties which can be converted into claims
RFC 7662 talks about OAuth2/OIDC servers returning token introspection responses.
Keycloak also implements it: https://issues.jboss.org/browse/KEYCLOAK-2266
Having such a factory will let the users (optionally) integrate with any certified OIDC servers. It will also allow to support the encrypted tokens issued by such servers (which choose to encrypt them) since importing the private keys of these providers into MP-JWT endpoints is not possible.
The text was updated successfully, but these errors were encountered: