Open gabriel-milan opened 2 years ago
I am experiencing exactly the same, when defining whitelist(s) on rules, they seem to be totally discarded. Not only do they not show up in the logged config on startup, but everyone keeps access.
I could not get defined domains on specific rules working either. Only global settings are being used on the latest image.
I am experiencing exactly the same, when defining whitelist(s) on rules, they seem to be totally discarded. Not only do they not show up in the logged config on startup, but everyone keeps access.
I'm facing the same problem. A rule with a whitelist is getting ignored entirely, everyone gets access.
I solved this problem by using the latest
tag for this image instead of 2
as recommended in the README.
I have been trying to get rules with a whitelist working... I have tried different image versions and nothing seems to work.
This is my config:
`Traefik-Forward-Auth:
container_name: Traefik-Forward-Auth
hostname: Traefik-Forward-Auth
image: thomseddon/traefik-forward-auth:latest
restart: always
networks:
IoT:
ipv4_address: 10.1.11.253
environment:
auth.${DOMAIN}
)No matter what I do when I check the logs any request against file.${DOMAIN} does not show it using the File rule. It instead shows it using the default rule.
Hello there, first of all thanks for the amazing project!
I've been facing some issues on the
traefik-v2/kubernetes/advanced-separate-pod
example.When I set a "global" whitelist on my
traefik-forward-auth.ini
file, such as:it works fine! But, unfortunately, when I try to do:
it doesn't. In the logs I can see that no
whitelist
has been set for thewhoami
rule:(a little prettier now)
This leads me to the following error:
As you can see, it's going through the correct rule, but unfortunately it's not setting any whitelist for it.
Am I missing something on my config file?