a6-plugin-wolf-rbac

Configure and enforce Wolf RBAC across APISIX routes using the a6 CLI.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/api7/a6 --skill a6-plugin-wolf-rbac-api7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-plugin-wolf-rbac
Source: https://github.com/api7/a6/tree/main/skills/a6-plugin-wolf-rbac
Command: npx skills add https://github.com/api7/a6 --skill a6-plugin-wolf-rbac-api7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes role-based access control across multiple APISIX deployments by integrating Wolf RBAC with the a6 CLI, enabling consistent authentication and per-resource permissions.

Core Features & Use Cases

  • Centralized authentication and URL+method permission checks across APISIX routes
  • Token management and login/user-info/change-password endpoints
  • Multi-application support with per-app consumers and header injection for authenticated users

Quick Start

Configure a Wolf RBAC-enabled consumer in a6 and attach it to a protected route to enforce RBAC across apps.

Frequently Asked Questions about a6-plugin-wolf-rbac

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

FAQPage Schema
How do I enforce centralized RBAC authorization across multiple APISIX deployments?

You can enforce centralized RBAC authorization across APISIX by integrating the Wolf RBAC server via the a6 CLI, enabling consistent authentication and per-resource permission checks across multiple deployments.

How do I configure APISIX consumer token management for a Wolf RBAC application?

Configuring APISIX consumer token management for Wolf RBAC requires setting up a specific consumer per application in a6 and attaching the configured consumer to protected routes to handle login endpoints.

Does APISIX RBAC authorization with Wolf require a separate server running?

Yes, APISIX RBAC authorization with Wolf requires a Wolf RBAC server to be available alongside properly configured a6 consumer settings to perform access checks and manage public endpoints.

How does Wolf RBAC handle user information and password changes in APISIX routes?

Wolf RBAC handles user information and password changes in APISIX by injecting user headers into authenticated requests and exposing dedicated login, user-info, and change-password endpoints within the authorization flow.

What are the limitations of using Wolf RBAC for APISIX route protection?

Limitations of using Wolf RBAC for APISIX route protection include the strict dependency on Wolf RBAC server availability and the requirement to properly configure a specific a6 consumer for each application to execute access checks.