Apisix-dashboard: discuss: improve the UE of config Authentication plugins

[liuxiran]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [x] 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 or 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 in consumer module.
   

2. the authentication plugins should be only shown with a switch to enabled/disabled in route or service module.
   

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

[liuxiran]

@juzhiyuan @LiteSun @bzp2010

[juzhiyuan]

Got your point, you mean for Auth plugins, we should only config it in Consumer instead of Route, and we COULD choose to enable or disable it in Route instead of cobfig, right?

I agree to this proposal, how about others suggestions?

cc @membphis @nic-chen @moonming ?

[membphis]

agree with this proposal too.

https://github.com/apache/apisix/issues/2308 , if we support this feature, the dashboard will easier.

[nic-chen]

agree +1

[liuxiran]

Got your point, you mean for Auth plugins, we should only config it in Consumer instead of Route, and we COULD choose to enable or disable it in Route instead of cobfig, right?

I agree to this proposal, how about others suggestions?

cc @membphis @nic-chen @moonming ?

yes you got my point @juzhiyuan 🤝, and furthermore, if the authentication plugin can be turned into the consumer’s default support plugin, just like proxy-rewrite in route, that would be better, but the cost of plugin modification may be higher

[juzhiyuan]

yep, let's implement your proposal first :D

[juzhiyuan]

I just put this feature in M1.7.

[juzhiyuan]

I checked this issue once more, and it seems that the backend should support this feature too 🤔 @liuxiran @membphis right?

[liuxiran]

I checked this issue once more, and it seems that the backend should support this feature too @liuxiran @membphis right?

thanks for @juzhiyuan 's reminder, I also rethinked this issue, and IMHO, it is better to get support from BE:

• get whether the plugin needs to be config together with category of all plugins instead of only get plugin names from GET /apisix/admin/plugins

whether the plugin needs to be config could also not be a specific flag, FE can also judge from whether the [plugin].schema.properties is empty, in this case , api should return the schema at the same time.

This would also apply to other plugins that do not require configuration :)

[juzhiyuan]

This solution works for me, but it seems that there still has also a lot of work to do, could you please take a look at this issue? cc @membphis @tokers.

[membphis]

We can create a new API to return all the information of the plug-in, such as schema, type, priority, etc.

For example the new API: /apisix/admin/plugins/meta_attributes, we need to discuss it on the mailing list first.

@liuxiran would like to handle this job?

[liuxiran]

We can create a new API to return all the information of the plug-in, such as schema, type, priority, etc.

For example the new API: /apisix/admin/plugins/meta_attributes, we need to discuss it on the mailing list first.

@liuxiran would like to handle this job?

sure, I have already sent a mail to dev, just waiting for others' comments and suggestions :)

[juzhiyuan]

Hi folks, final conclusion here?

[membphis]

@liuxiran I think we can close this issue and create a new one with the final conclusion from the emailing list.

[liuxiran]

@liuxiran I think we can close this issue and create a new one with the final conclusion from the emailing list.

got it , and as we talked yesterday., this issue would be move to M2.3, right? @membphis

[membphis]

yes, confirm this @liuxiran

[juzhiyuan]

any update?

[liuxiran]

after the new api GET /plugins?all=ture finished, I will open a new issue to trace the process. close it now.