Replies: 4 comments 1 reply
|
Just found this because I have the same problem. Did you find any solution? |
0 replies
|
Following |
0 replies
|
I used this guide and it's working perfectly. https://forum.hhf.technology/t/implementing-geoblocking-in-pangolin-stack-with-traefik/490 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello!
I am attempting to configure rules to meet specific geo-access and authentication requirements, but I am running into a limitation based on how rules are matched.
My Goal: I need to enforce the following hierarchy of access control for my service:
The Conflict: Since rules are processed from top to bottom in order of priority, I need to differentiate actions for requests originating from KZ based on the path before the final global Deny Rule executes.
If I set up an Allow Rule based only on Path = /api/, this rule allows all countries to bypass authentication for API access, which violates my requirement to block all non-KZ traffic.
Conversely, if I try to use a Country rule, I cannot separately apply an Allow action to the API path (/api/) while simultaneously requiring a Pass to Auth action for the standard UI paths from the same country (KZ).
Question: If I can't use a compound rule (e.g., Country = KZ AND Path = /api/*), how can I do it in another way? Or is it even possible?😅
I don't want to open my API to the whole world :\
All reactions