kayx23 opened a new pull request, #13943: URL: https://github.com/apache/apisix/pull/13943
### Description This updates the English and Chinese `jwt-auth` documentation to use a current, reproducible HashiCorp Vault workflow. - replace the discontinued `vault:1.9.0` image with `hashicorp/vault:1.21.4` - connect APISIX and Vault through a dedicated Docker network instead of an unreachable loopback address - document Vault dev mode as local testing only and retain the production least-privilege token boundary - configure Vault KV version 1 and store the signing secret before referencing it from APISIX - replace the unsupported ADC top-level `secrets` configuration with a working hybrid flow: create the Secret through the Admin API, then configure the Consumer, Credential, and Route through the Admin API or ADC - verify the authenticated Consumer and Credential headers - keep the English and Chinese procedures aligned ### Validation - tested the exact workflow with APISIX 3.18.0 and `hashicorp/vault:1.21.4` - confirmed Vault KV version 1 and the stored secret value - confirmed the Admin API Secret, Consumer, Credential, and Route requests succeed - tested ADC 0.24.2 and 0.29.0 lint and synchronization - verified the documented JWT returns `X-Consumer-Username: jack` and `X-Credential-Identifier: cred-jack-jwt-auth` - parsed the changed YAML and JSON examples and checked tab balance - ran `markdownlint` and `git diff --check` ### References - https://developer.hashicorp.com/vault/docs/updates/deprecation#duplicative-docker-images - https://developer.hashicorp.com/vault/docs/concepts/dev-server - https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
