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/12/30 02:33:52 UTC

[GitHub] [apisix] whioue commented on issue #8582: feat: After using the consumer-restriction plugin on the service, the authentication type of the referenced consumer is modified. The system does not add verification

whioue commented on issue #8582:
URL: https://github.com/apache/apisix/issues/8582#issuecomment-1367691663

   > @whioue Thanks for your kind advice.
   > 
   > Totally the auth config of `Consumer` should be the same as the `Route` you want to make it sense, so that the auth type should be changed both of the two simultaneously by hand.
   > 
   > The current solution is not able to cascade the configuration of both sides, but it is still acceptable to use.
   > 
   > Of course, an outright ban on modifications on the consumer side is certainly possible. But it also disallows changes to other consumer attributes, such as desc, and so on.
   > 
   > If you have a better idea, you can write a proposal to the community to expand on that. : )
   
   请问为什么 “完全禁止在consumer方面进行修改当然是可能的。但它也不允许更改其他消费者属性,例如 desc 等”。我认为相同认证类型的情况下,应该可以修改consumer的其他属性吧,会有别的影响吗?


-- 
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