Scenario: need to protect vscode browser version (that runs in electron); I will display it using an iframe.
Tried basic auth (username+password), but it's not a fit. Tried the middleware option - "traefik.http.middlewares.auth.forwardauth.address=http://auth:4181/auth", which causes my some very strange problems...
Any simple option on Earth that can protect my service using a query param like ?password=x or a simple header 'key=x'?
Scenario: need to protect vscode browser version (that runs in electron); I will display it using an iframe.
Tried basic auth (username+password), but it's not a fit. Tried the middleware option - "traefik.http.middlewares.auth.forwardauth.address=http://auth:4181/auth", which causes my some very strange problems...
Any simple option on Earth that can protect my service using a query param like ?password=x or a simple header 'key=x'?
Share Improve this question asked Mar 21 at 8:58 johnykesjohnykes 2,0132 gold badges11 silver badges36 bronze badges1 Answer
Reset to default 0No integrated Traefik middleware for that. You can check the list of plugins for Traefik.
I doubt that it will be that easy, because you will have multiple requests for dependencies, which might not include the initial query param or header, so you probably need to establish a session with a cookie.
Maybe try with ForwardAuth again, I just created a test setup with a dummy node.js auth container, maybe you can adapt that for your requirements and add a session cookie.