-
Notifications
You must be signed in to change notification settings - Fork 1.2k
HTTP Basic Auth and set-xauthrequest #658
Comments
If you use You can get the username from
|
Right, only I guess this leaves me with 3 options:
|
I guess I need to learn more about HTTP headers. Although my backend application states "Basic Web Authentication" it does not look only for the Interestingly enough, I didn't know that the RFC requires I think that answers my question. Thank you so much for the quick and very helpful response! |
I'm glad you got it working :) |
Hi,
I have oauth2_proxy sitting in front of Cacti. Cacti support "web based authentication" where the webserver performs basic authentication and supplies the username to Cacti via the "Authentication" header.
In my particular configuration, I am using nginx as a reverse proxy, with authentication delegated to oauth2_proxy using the "ngx_http_auth_request_module" module in nginx.
Cacti complains about not being able to find lack of "Authentication" header and username not being passed to Cacti. Will oauth2_proxy provide the "Authentication" header for every request?
For oauth2_proxy I have "-pass-basic-auth" explicitly enable although docs state that default is "true". Here is my location block in nginx. Note that authentication is fine, just user isn't passed to Cacti.
One last note, if I force a static "Authentication" by setting within the location block all works fine. This would be a line such as:
proxy_set_header Authorization "Basic dXNlcjpwYXNzd29yZA==";
With the line provided, the username and password would be "user/password".
Thanks,
Adi
The text was updated successfully, but these errors were encountered: