ddd4j-quarkus Auth

Overview

Covers JWT, OIDC, Shiro, Sa-Token, SubjectProvider, RolesAllowed, and request scope uniformly, not split per artifact. Choose 3.3.x or 4.0.x first, then read the current source.

When to Use

• Choosing among JWT, OIDC, Shiro, and Sa-Token for a ddd4j-quarkus service against its deployment model.
• Registering exactly one primary SubjectProvider via CDI and mapping identities to AuthPrincipal with explicit role/permission rules.
• Applying RolesAllowed and mapping security exceptions to stable error responses.
• Binding the Subject at request start and restoring it on success, exception, and async completion paths.
• Verifying anonymous, valid, expired, and insufficient-role paths with QuarkusTest on either line.
• Reviewing existing auth wiring (duplicate providers, missing expiry tests, printed secrets) on the 3.3.x or 4.0.x line.

When NOT to Use

Do not use this skill when: