a6-plugin-basic-auth

Configure APISIX basic-auth by creating a consumer, attaching credentials, and binding the plugin to target routes via the Admin API or a6 CLI. This enforces route-level access control by validating submitted credentials against registered consumer profiles.

HTTP Basic Authentication secures API access by requiring a username and password in the request header. You need it when protecting API routes with simple credential binding to APISIX consumers without complex token generation or OAuth flows.

Yes, APISIX basic-auth supports the hide_credentials option. Enabling this removes the authentication header from the request before forwarding it to upstream services, preventing credential leakage to backend systems.

The anonymous_consumer feature provides a fallback for unauthenticated requests. It allows users without valid basic-auth credentials to access routes under a default identity, often paired with rate-limiting policies to restrict anonymous traffic behavior.

Yes, the a6 CLI supports APISIX consumer management and route plugin configuration. You can use a6 commands to create consumers, attach basic-auth credentials, and apply plugin bindings to specific routes.

HTTP Basic Authentication transmits credentials encoded in plaintext, requiring HTTPS to secure transit. It lacks token expiration and granular scope control, making it less suitable for complex authorization scenarios compared to JWT or OAuth mechanisms.