quarkus-security

Implement JWT/OIDC authentication, RBAC authorization, and input validation for Quarkus Java applications.

3|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill quarkus-security-keyvaluesoftwaresystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quarkus-security
Source: https://github.com/KeyValueSoftwareSystems/maestro/tree/main/skills/stacks/java/quarkus-security
Command: npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill quarkus-security-keyvaluesoftwaresystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of implementing enterprise-grade security in Quarkus applications, ensuring consistent protection against common vulnerabilities like unauthorized access, SQL injection, and insecure data handling.

Core Features & Use Cases

  • Authentication & Authorization: Implements JWT, OIDC, and RBAC patterns using standard Quarkus security annotations.
  • Input Validation & Protection: Provides patterns for Bean Validation, custom constraints, and parameterized queries to prevent injection attacks.
  • Security Hardening: Includes configurations for CORS, security headers, rate limiting, and audit logging to meet compliance requirements.

Quick Start

Ask the assistant to review your current Quarkus security configuration and apply the recommended authentication and input validation patterns provided in this skill.

Frequently Asked Questions about quarkus-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement JWT and OIDC authentication in a Quarkus Java application?

JWT and OIDC authentication in a Quarkus Java application is implemented using standard Quarkus security annotations to establish robust RBAC patterns. This approach integrates token validation directly within your microservices.

How do I prevent SQL injection in Quarkus microservices?

Preventing SQL injection in Quarkus microservices involves applying Bean Validation, custom constraints, and parameterized queries. These input validation patterns protect against unauthorized access and insecure data handling.

Does Quarkus support OWASP-compliant security headers and rate limiting?

Quarkus supports OWASP-compliant security headers and rate limiting through specific security hardening configurations. Implementing these patterns alongside audit logging ensures your application meets enterprise compliance requirements.

What is the best way to manage secrets and environment variables for Quarkus security?

Managing secrets for Quarkus security is best handled via Vault or environment variables. Secure secret management prevents unauthorized access and ensures consistent protection of sensitive application data.

Can I configure CORS and audit logging for enterprise Quarkus applications?

CORS and audit logging can be configured for enterprise Quarkus applications as part of security hardening. These features satisfy compliance requirements and ensure consistent protection against common vulnerabilities.

How do I enforce role-based access control in Quarkus?

Role-based access control in Quarkus is enforced using standard security annotations combined with JWT and OIDC integration. This establishes robust authorization policies for your secure microservices.