Skip to content
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

Issues with AWS Authorization header #218

Open
gmaxwell94 opened this issue Apr 29, 2019 · 1 comment
Open

Issues with AWS Authorization header #218

gmaxwell94 opened this issue Apr 29, 2019 · 1 comment

Comments

@gmaxwell94
Copy link

gmaxwell94 commented Apr 29, 2019

AM trying to up put a ldap front end to AWS Kibana, Have the proxy working, have the ldap working but when used together, get warning.

{"message":"
Authorization header requires 'Credential' parameter.
Authorization header requires 'Signature' parameter.
Authorization header requires 'SignedHeaders' parameter.
Authorization header requires existence of either a 'X-Amz-Date' or a 'Date' header.
Authorization=Basic Z21heHdlbGxAbW9iaWxlaXJvbi5jb206cGFzc3dvcmQ="}

The fix for amazon in Nginx is to set
proxy_set_header Authorization "";

which of course breaks the ldap auth.

Is there some way to change the name of the Authorization head as it gets sent to Amazon in either the ldap header WWW-Authenticate-
line 1779 r->headers_out.www_authenticate->key.data = (u_char *) "WWW-Authenticate";
or in Nginx config.
Thanks in advance for the help. Really surprised that this set up does not already exists.

@Harrtron
Copy link

Did you ever manage to resolve this, @gmaxwell94 ? Having the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants