[MXS-4190] DBfirewallfilter portability Created: 2022-07-05 Updated: 2023-09-05 Resolved: 2022-09-08 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | dbfwfilter |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Sylvain ARBAUDIE | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The functionalities from dbfwfilter are appreciated and put to good use by quite a few customers. As agnostic as i am about where to place it, i really think this piece of functionailities should stay in the MariaDB ecosystem. it could belong in the server itsefl, stay a service filter or even become linked to servers these would all make sense. |
| Comments |
| Comment by markus makela [ 2022-07-05 ] |
|
Converted to a New Feature. We use Tasks for tracking things that don't fall under either features or bugs. |
| Comment by Sylvain ARBAUDIE [ 2022-08-03 ] |
|
First of all : sorry for the slow reaction. About the main topic, i have clients who actually use the dbfirewall filter of maxscale, and some also wanted to but stop their project due to the news of deprecation. They all use the rulebook to also reviewing an ER from sokrates i found out another use case : |
| Comment by Sylvain ARBAUDIE [ 2022-08-03 ] |
|
I am actually online with a french client who needs to put restriction on specific table/column access for specific users. MXS dbfirewallfilter would be great since it can just do that, easier than using the native mariadb privilege system. |
| Comment by Sylvain ARBAUDIE [ 2022-08-04 ] |
|
they want to prevent any function usage froma specific login |