You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/09/08 06:29:38 UTC
[GitHub] [apisix] foliet opened a new issue, #7885: feat: Allows the payload in the jwt token to be added to the upstream request body
foliet opened a new issue, #7885:
URL: https://github.com/apache/apisix/issues/7885
### Description
Why can the jwt token only carry the payload when it is generated, but cannot put the payload in the request body to the upstream service when it is parsed?
If I want to pass the jwt token to the upstream service for parsing, what is the meaning of this plugin?
I hope that the key that will be added to the request body in the jwt payload can be set in the jwt plugin configuration of the router.
--
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: notifications-unsubscribe@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] foliet closed issue #7885: feat: Allows the payload in the jwt token to be added to the upstream request body
Posted by GitBox <gi...@apache.org>.
foliet closed issue #7885: feat: Allows the payload in the jwt token to be added to the upstream request body
URL: https://github.com/apache/apisix/issues/7885
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] foliet commented on issue #7885: feat: Allows the payload in the jwt token to be added to the upstream request body
Posted by GitBox <gi...@apache.org>.
foliet commented on issue #7885:
URL: https://github.com/apache/apisix/issues/7885#issuecomment-1240331744
I hope the authentication can be stateless without having to store another user information in etcd
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #7885: feat: Allows the payload in the jwt token to be added to the upstream request body
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #7885:
URL: https://github.com/apache/apisix/issues/7885#issuecomment-1244894403
> but cannot put the payload in the request body to the upstream service when it is parsed?
jwt-auth just validates jwt and doesn't require modifying the request body. Or this will break the original request and is not standard behavior.
> If I want to pass the jwt token to the upstream service for parsing, what is the meaning of this plugin?
jwt would pass to upstream. I suggest you read the documentation first: https://apisix.apache.org/docs/apisix/plugins/jwt-auth/
> I hope that the key that will be added to the request body in the jwt payload can be set in the jwt plugin configuration of the router.
From a personal point of view, I don't like this feature, it goes beyond the boundaries of authentication.
--
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: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org