-
Task
-
Resolution: Done
-
Critical
-
None
-
8
-
False
-
-
False
-
-
-
Quarkus Upstream Docs Sprint 7, Quarkus Upstream Docs Sprint 8, Quarkus Upstream Docs Sprint 9, Quarkus UpstreamDocs Sprint 10, Quarkus Upstream Docs Sprin 11, Quarkus Docs Sprint 12, Quarkus Docs Sprint 13, Quarkus Docs Sprint 14, Quarkus Docs Sprint 15, Quarkus Docs Sprint 16
During the final editing work and peer reviews in sprint 5/6 we made lots of improvements downstream git lab source. We need to update the existing upstream security doc source with many of these essential style edits. (not the Red Hat specific edits).
This task can begin when the 2.13 security doc QE work is done and the security docs are published downstream
If we don't do this task:
- Upstream docs don't benefit from good styling updates that are downstream.
- The next downstream import of this content for 3.0 docs will take longer.
Topics done (Done = Edited to ensure harmonious style downstream , changes approved merged to upstream main before 3.2 cut off )
- Quarkus Security Architecture
- Quarkus Security Overview
- Quarkus authentication mechanisms
- Authorization of web endpoints
- Security Identity Providers
- Security vulnerability detection and reporting in Quarkus
- Basic authentication
- Enable Basic authentication
- Secure a Quarkus application with Basic authentication and Jakarta Persistence
- Proactive authentication
- OpenID Connect authorization code flow mechanism for protecting web applications