You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: