Sched is temporarily in maintenance Read-Only mode. You can continue using the event and personal schedule, but will not be able to make any changes. We apologize for the inconvenience.
The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered forCloudNativeSecurityCon North America 2024 to participate in these sessions. If you have not registered but would like to join us, please go to the event registration page to purchase a registration.
Please note: This schedule is automatically displayed in Pacific Daylight Time (PDT), UTC -7. To see the schedule in your preferred timezone, please select from the drop-down menu to the right, above "Filter by Date."
Using OAuth2 access tokens is the best practice for authenticating an API request by a resource server. As stated in the draft CNCF Zero Trust White Paper, it is recommended to verify the "audience" of the access token to prevent access tokens from being consumed by other recipients ("Token Redirect" attack). Especially in cloud-native architectures, there are many internal workloads, so it's hard for the resource owner to identify all audiences and consent for each consumption. In this case, we can adopt the OAuth WG's draft called "Transaction Tokens" (Txn-Tokens), which utilizes OAuth2 Token Exchange (RFC8693) to issue Txn-Tokens that allow downstream workloads to identify call chains. Keycloak, an IAM OSS, supports Token Exchange. Therefore, Keycloak can potentially support the Txn-Token service which issues Txn-Tokens. In this presentation, Yoshiyuki Tabata provides an overview of Txn-Tokens and introduces how to implement Txn-Tokens with Keycloak.
Yoshiyuki Tabata is an OSS consultant specializing in IAM, API platforms, and cloud-native security. He serves as Tech Lead of CNCF TAG Security and Compliance, is a CNCF Ambassador, and is a Project Lead and author of the CNCF IAM Whitepaper. He is also a recipient of the 2026 CNCF... Read More →