Securing Your Quarkus Applications
summary
A live coding session builds a Quarkus app, adds the quarkus-oidc extension and runs a local Keycloak dev server, creates users (alice/bob) and roles, and enforces @RolesAllowed on endpoints. It shows injecting SecurityIdentity and JWT claims into request handlers, configures a second Quarkus service to use the same OIDC server, and demonstrates automatic token propagation between services using the Quarkus REST client; IDE issues occur but authentication, role checks and inter-service token propagation work end-to-end.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:48Security key concepts
- 5:46Demo: Quarkus project setup
- 15:18Keycloak authentication
- 20:23Identity management
- 24:44Identity injection risks
- 28:17Secure propagation between services
- 32:22Summary and Q&A
related talks
31mSecure your Quarkus Applications
35mQuarkus Security for Spring developers
52mIntroduction to Quarkus Security
52mA day in the life of a Quarkus developer
36mA day in life of a Quarkus developer
48mIntegration Testing with Quarkus.
25mFine-Grained Authorization & Beyond: Mastering Keycloak Patterns in AI-infused Apps
37mQuarkus in Action…in Action!