Uses of Interface
org.keycloak.broker.provider.ClientAssertionIdentityProvider
Packages that use ClientAssertionIdentityProvider
Package
Description
-
Uses of ClientAssertionIdentityProvider in org.keycloak.broker.oidc
Classes in org.keycloak.broker.oidc that implement ClientAssertionIdentityProvider -
Uses of ClientAssertionIdentityProvider in org.keycloak.broker.spiffe
Classes in org.keycloak.broker.spiffe that implement ClientAssertionIdentityProviderModifier and TypeClassDescriptionclass
Implementation for https://datatracker.ietf.org/doc/draft-schwenkschuster-oauth-spiffe-client-auth/ Main differences for SPIFFE JWT SVIDs and regular client assertions:jwt-spiffe
client assertion typeiss
claim is optional, uses SPIFFE IDs, which includes trust domain insteadjti
claim is optional, and SPIFFE vendors re-use/cache tokenssub
is a SPIFFE ID with the syntaxspiffe://trust-domain/workload-identity
Keys are fetched from a SPIFFE bundle endpoint, where the JWKS has additional SPIFFE specific fields (spiffe_sequence
andspiffe_refresh_hint
, the JWK does not set thealg>
-
Uses of ClientAssertionIdentityProvider in org.keycloak.social.gitlab
Classes in org.keycloak.social.gitlab that implement ClientAssertionIdentityProvider -
Uses of ClientAssertionIdentityProvider in org.keycloak.social.google
Classes in org.keycloak.social.google that implement ClientAssertionIdentityProvider -
Uses of ClientAssertionIdentityProvider in org.keycloak.social.linkedin
Classes in org.keycloak.social.linkedin that implement ClientAssertionIdentityProviderModifier and TypeClassDescriptionclass
Specific OIDC LinkedIn provider for Sign In with LinkedIn using OpenID Connect product app.