Bring your self-made user JWT with Keycloak OIDC.
Shows how to mint a self-issued JWT signed with an x.509 key pair, register that same key as an OIDC provider in a Keycloak realm, and pass the JWT in the x-user-token header of a SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp find-destination call so it returns a signed SAML bearer assertion for a mock destination configured with Authentication: SAMLAssertion. The JWT is generated by a Node.js function on SAP BTP, Kyma runtimeSAP BTP, Kyma runtimeA fully managed Kubernetes runtime on SAP BTP, based on the open-source project Kyma, where extensions to SAP solutions run as containerised microservices and serverless Functions.sap official, btp, and the destination's x_user_token.jwks_uri points at the Keycloak realm's certs endpoint so the service can verify the token before issuing the assertion. The target use is unattended user-identity propagation from edge devices that cannot be registered with a full identity provider.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · connectivity-tag.
For your agent
- Ref
content:bring-your-self-made-user-jwt-with-keycloak-oidc- JSON
- /content/bring-your-self-made-user-jwt-with-keycloak-oidc.json
- MCP
- Connecting an agent