wallacezhou opened a new issue, #21615: URL: https://github.com/apache/shardingsphere/issues/21615
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? v5.2.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior use authority type DATABASE_PERMITTED in ShardingSphere-Proxy 5.2.0, config two accounts testacc_a，testacc_b config account testacc_a to access logic db testdb_a, account testacc_b to access logic db testdb_b expected that both two accounts can access ShardingSphere Proxy via mysql ui tools eg. workbench or navicat ### Actual behavior only account testacc_a access ShardingSphere Proxy via mysql ui tool successfully, the other account testacc_b failed to access ShardingSphere Proxy via mysql ui tool ### Reason analyze (If you can) when connect with account testacc_a, the sql only query logic db testdb_a but when connect with account testacc_b , there would be one or more sql that would query logic db testdb_a, as testacc_b is configed to access logic db testdb_b, it cannot found db testdb_a accss testdb_a will cause the unknow database error like below in ShardingSphere Proxy log, connect use testacc_b, error log like below:   in sharding proxy version 5.1, config use SCHEMA_PRIVILEGES_PERMITTED has no this issue ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. config rules in file server.yaml rules: - !AUTHORITY users: - testacc_a@:123456 - testacc_b@:123456 provider: type: DATABASE_PERMITTED props: user-database-mappings: testacc_a@=testdb_a,testacc_b@=testdb_b add config file config-sharding.yaml and config-testdb_a.yaml, config-testdb_a.yaml： databaseName: testdb_a config-testdb_a.yaml: databaseName: testdb_b add dataSources for the two files, the dataSources can be the same or different ### Example codes for reproduce this issue (such as a github link). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
