Jakarta EE Security - Sailing Safe in Troubled Waters
summary
Jakarta EE 10 actually ships OpenID Connect built into Jakarta Security, layering a developer-facing Jakarta Security API over lower-level Jakarta Authentication and Jakarta Authorization SPIs. Examples show hardcoded identity stores (user "Duke" → roles "fu,bar"), form and REST API-key auth, and role checks via @RolesAllowed. Compatible runtimes listed: Soteria, Exousia, GlassFish and Tomcat. A live demo tries to run OpenID Connect but fails at runtime due to a TLS/cert error, so slides and code links are provided instead.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:02Common Principles
- 5:41Jakarta Authentication Authentication Mechanism
- 7:49Jakarta Security Creating Secure Applications
related talks
48mJakarta EE 10 Feature by Feature
45mOpenIDConnect Has Finally Come to Jakarta EE!
51mJakarta EE 10 and Beyond
02h 38mJakarta in 2023, What Is the Situation?
46mJakarta EE 11: Going Beyond the Era of Java EE
43mJakarta EE 9 and Beyond
50mJakarta EE 10: Modern & Lightweight Cloud Application Development
15mJakarta EE: Why and how to get involved in Open Source Software?