You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to access the JWT authentication sign endpoint exposed through the public API, a 404 Not Found error is returned.and public-api is enabled both in apisix config.yaml and apisix-dashboard config.yaml
Environment
APISIX version (run apisix version):apache/apisix:3.11.0-debian
Operating system (run uname -a):Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
OpenResty / Nginx version (run openresty -V or nginx -V):
etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):bitnami/etcd:3.5.16
APISIX Dashboard version, if relevant:apache/apisix-dashboard:3.0.1-alpine
Plugin runner version, for issues related to plugin runners:
LuaRocks version, for installation issues (run luarocks --version):
The text was updated successfully, but these errors were encountered:
@Fsystem as of now, I don't think APISIX provide any out-of-the-box. However, you can always write a custom plugin, e.g. jwt-sign, and expose a public api the same way that jwt-auth did (you can copy or adapt the code from the commit I provided above).
Description
When attempting to access the JWT authentication sign endpoint exposed through the public API, a 404 Not Found error is returned.and public-api is enabled both in apisix config.yaml and apisix-dashboard config.yaml
Environment
apisix version
):apache/apisix:3.11.0-debianuname -a
):Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linuxopenresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):bitnami/etcd:3.5.16luarocks --version
):The text was updated successfully, but these errors were encountered: