liuxiran opened a new issue #529:
URL: https://github.com/apache/apisix-dashboard/issues/529


   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [ ] Bug
   - [ ] Requirements
   - [ ] Feature or performance improvement
   - [ ] Other
   
   ___
   ### Why
   The Authentication plugins, e.g: `basic-auth` `openid-connect` and other 
auth plugins supported by Apisix should work with consumer together. Only when 
one auth plugin is enabled and configed correctly can a consumer be created or 
modified, and can access a route which is also enabled the same auth plugin. At 
the same time, a route of a service can enabled the auth plugin  without any 
configs(even if configured here, the auth plugin configuration of consumer will 
 matched by default).
   
   RIght now, the auth plugins can be configed both in consumer and route, but 
the auth config in route doesn't really work, and it will Induce user that only 
the configed consumer can access the route. So it would be better to improve 
the UE of config auth plugins.
   
   ### Proposal
   
   1. the authentication plugins should be enabled with configuration.
   ![2020-09-30 
10-44-11屏幕截图](https://user-images.githubusercontent.com/2561857/94637854-2843fd00-030b-11eb-96bf-0029ab13105a.png)
   
   
   1. the authentication plugins should be only shown with a switch to 
enabled/disabled.
   ![2020-09-30 
10-44-11屏幕截图](https://user-images.githubusercontent.com/2561857/94637879-33972880-030b-11eb-9177-3363b573ae96.png)
   
   1. right now if a route enabled two auth plugins, it should be matched with 
this two auth token, In fact, it is not possible for users to access the same 
route using two or more different authentication methods. so it would be better 
to only enabled one auth plugin in route (or ).


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to