Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guard Rail doesn't work for native connections #616

Open
djbe opened this issue Dec 23, 2024 · 2 comments
Open

Guard Rail doesn't work for native connections #616

djbe opened this issue Dec 23, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@djbe
Copy link

djbe commented Dec 23, 2024

Trying to set up any sort of guard rail to block certain inputs.

  • Tried the default password blocklist
  • Tried the default delete-with-where regex
  • Tried a custom regex rule

In every case, the guard rail works fine in the web interface, there I get

validation error, match guard rails input rule, type=pattern_match, pattern=…

But when I use a native connection (using hoop connect …), the queries just work and are not blocked at all.

Some more info:

  • webapp version 1.35.1
  • gateway version 1.31.10
  • connection: tried both MySQL & PostgreSQL, using the default agent
@djbe
Copy link
Author

djbe commented Dec 23, 2024

Ah just noticed we seem a few versions behind 🤦 Let me see if updating solves the issue.

Edit: updated from 1.30.4 -> 1.31.10, still doesn't work as expected.

@sandromello sandromello added the enhancement New feature or request label Dec 27, 2024
@sandromello
Copy link
Contributor

Hello, thank you for reporting this issue. We still don't support guard rail rules for native connections. I will mark this issue as a possible enhancement for the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants