quarkus-security

Implement authentication, authorization, and input validation for Quarkus applications.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill quarkus-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quarkus-security
Source: https://github.com/sakamoto-family-smile/agent_monorepo/tree/main/.claude/skills/ecc/quarkus-security
Command: npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill quarkus-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Misconfigurations and insecure defaults in Quarkus applications can lead to authentication weaknesses, authorization gaps, and data exposure. The Skill consolidates security best practices across authentication, authorization, validation, secrets management, and dependency scanning to reduce risk.

Core Features & Use Cases

  • Authentication & Authorization: guidance for JWT/OIDC, Basic Auth, and Role-Based Access Control.
  • Input Validation & Data Integrity: Bean Validation and custom validators to enforce data quality.
  • Secrets & Dependency Security: guidelines for managing secrets and scanning dependencies to reduce risk.
  • Security Headers & CORS: recommended headers and CORS settings for hardening endpoints.
  • Use cases include securing REST endpoints, protecting microservices, and enforcing RBAC in Quarkus apps.

Quick Start

Apply these security guidelines to your Quarkus service during initial setup and configuration.

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 Quarkus?

To implement JWT and OIDC authentication in Quarkus, apply security best practices for configuring tokens, managing user sessions, and enforcing access controls to protect your backend services.

What's the best way to enforce Role-Based Access Control in Quarkus microservices?

Enforcing Role-Based Access Control in Quarkus involves applying programmatic security checks and authorization rules across microservices to restrict endpoint access based on user roles.

How does Bean Validation work for securing Quarkus REST endpoints?

Bean Validation secures Quarkus REST endpoints by applying custom validators and data integrity checks to user inputs, ensuring data quality and preventing injection attacks.

Can I use environment variables for secrets management alongside Quarkus security?

You can use environment variables for secrets management in Quarkus by integrating ENV configurations and Vault guidelines to securely handle application credentials.

Why add security headers and CORS configurations to Quarkus applications?

Adding security headers and CORS configurations to Quarkus applications hardens REST endpoints by mitigating cross-origin risks and enforcing browser-level security policies.

Does Quarkus security support dependency scanning to reduce application risk?

Quarkus security supports dependency scanning by providing guidelines to identify vulnerable libraries, reducing overall application risk and ensuring secure service operations.