Wolf RBAC Configuration
The wolf-rbac plugin authenticates requests through Wolf, enforces application permissions, and forwards verified user identity upstream. Configuration covers consumer fields and route and service fields.
Parameters
See plugin common configurations for configuration options available to all plugins.
Consumers
The following are plugin attributes available for configurations on consumers.
appid
Wolf application ID used to select this consumer. The application ID in the caller's RBAC token must match this value.
Required in APISIX 3.20.0 and API7 Enterprise from version 3.10.10. Earlier versions default to
unset.server
Wolf server origin, including the scheme and without a trailing slash. Use HTTPS and enable
ssl_verifyfor production traffic.ssl_verify
If true, verify the Wolf server's TLS certificate. An omitted value does not enable certificate verification.
Routes or Services
The following are plugin attributes available for configurations on routes or services.
header_prefix
Prefix for the
UserId,Username, andNicknameheaders populated from user information returned by Wolf. Before authentication, the gateway removes client-supplied request headers with these names. For permitted requests, it adds them to the upstream request and the client response.Available on routes and services in APISIX 3.20.0 and API7 Enterprise from version 3.10.10. Earlier versions configure
header_prefixon the consumer. See Upgrade.