-
Notifications
You must be signed in to change notification settings - Fork 268
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
traefik basic authentication broken with v2 #202
Comments
I know nothing about traefik so I won't be much of a help here. Hopefully someone with similar setup will be able to help. Also, someone reported that he had to disable nginx basic auth for v2.0: #179 (comment) |
Its probably the same issue then. I'll take a look and compare 1.7.4 and 2.0 cookies. I'll report back... |
Having similar issue but I'm using HAproxy ACL with http-request auth in my PFsense. Have no issue with other services until I updated Flame to the latest. |
It seems a conflict with the new password authentication - https://github.com/pawelmalak/flame/wiki/Authentication I'm still looking into it... |
Its a clash with JWT and the Authorization header field. Traefik, nginx and HAproxy use this header field for basic auth, but flame is using it for version 2.0. I guess a good conclusion would be for flame to implement an optional setting that offers the same username/password basic auth when first launching? Feature Request? |
I change Flame's Authorization header to Authorization-Flame here: ekremparlak@d9e9ef8 |
Looks like https://example.com/api/apps was same without changes |
Is there a possible fix? |
Can anyone pull |
Yes, ill test it now ... |
Confirmed working perfectly using basic auth on Traefik !! :) |
That's great. I'll have to test a few more things but it should be out with the next version. |
I use traefik to provide basic authentication in front of flame (loving it BTW!), which now continually prompts for the user/password details with the latest flame version. Reverting back to flame:1.7.4 removes the new issue.
I'm guessing it's a cookie issue somewhere with flame?
Flame docker labels used for traefik:
traefik.http.middlewares.traefik-basicauth.basicauth.users : USER:PASSWORD
traefik.http.middlewares.traefik.addprefix.prefix : traefik-basicauth
traefik basicauth doc link: https://doc.traefik.io/traefik/v2.0/middlewares/basicauth/
Happy to provide additional info and test any fixes.
The text was updated successfully, but these errors were encountered: