Configuring multiple access-control.properties in config.properties does not take effect

[A-little-bit-of-data]

According to the document description, multiple files were configured, as shown in the figure below. After restarting the coordinator, it was found that it did not take effect through the trino-cli connection, but it was shown in the log that it took effect.

But if you write only one property in the access-control.config-files in the config.properties file, and verify that the configuration takes effect through trino-cli query, has anyone encountered this situation? Or is there something wrong with my configuration?

### Tasks

[hirolee88]

What UI are you using? The issue is, there's Trino-admin on the left side, but results not, right?

What is the content of test.json?

[A-little-bit-of-data]

What UI are you using? The issue is, there's Trino-admin on the left side, but results not, right?

What is the content of test.json?

ui is superset, and Trino-admin represents the user who uses admin. The results on the right should see all catalogs, but only one system is seen. The content of test.json is as follows：

{ "catalogs": [ { "user": "tpcds", "catalog": "tpcds", "allow": "all" } ], "schemas": [ { "user": "tpcds", "catalog": "tpcds", "schema": "sf1|sf10", "owner": false } ], "tables": [ { "catalog": "tpcds", "schema": "sf1|sf10", "user": "tpcds", "table": ".*", "privileges": [ "SELECT", "INSERT", "DELETE", "UPDATE", "OWNERSHIP", "GRANT_SELECT" ] } ] }

[A-little-bit-of-data]

Has anyone encountered this problem before?

[A-little-bit-of-data]

The problem has been raised for several months. Hasn't the official noticed this problem?