You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/10/01 08:31:07 UTC
[GitHub] [shardingsphere] natehuangting opened a new issue, #21300: Proxy increases access control
natehuangting opened a new issue, #21300:
URL: https://github.com/apache/shardingsphere/issues/21300
## Feature Request
The current permission control available for the proxy is basically `type: ALL_PERMITTED`. Can it be designed to be similar to
the following permission control to intercept various operations at the proxy layer.
The following configuration is in server.yaml.
```
rules:
- !AUTHORITY
users:
- root@%:root
- sharding@:sharding
- provider:
type: DEFINE_PERMITTED
props:
user-permitted:
root: super@all
sharding: delete,dump,update@logic_db1,logic_db2
```
--
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@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] RaigorJiang commented on issue #21300: Proxy increases access control
Posted by "RaigorJiang (via GitHub)" <gi...@apache.org>.
RaigorJiang commented on issue #21300:
URL: https://github.com/apache/shardingsphere/issues/21300#issuecomment-1407421878
This is good advice, I think the configuration API still needs to be designed.
--
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@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org