我有一个授权模块,每当向私有端点发出请求时都会调用该模块。
该模块从Authorization
标头中解析令牌,并且:
Authorization
标头中返回该令牌。“profile”是私有端点之一,它的配置方式如下:
location /profile {
auth_request /jwtverify;
auth_request_set $authorization $upstream_http_authorization;
proxy_set_header authorization $authorization;
proxy_pass http://private-profile:80;
}
Run Code Online (Sandbox Code Playgroud)
jwtverify
是这样配置的:
location = /jwtverify {
internal;
proxy_pass http://auth-module:8080/auth/verify;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-URI $request_uri;
auth_request_set $http_authorization $upstream_http_authorization;
}
Run Code Online (Sandbox Code Playgroud)
现在,除了要求号外,一切正常。3:如果auth模块设置了Authorization
header,客户端永远不会收到它。
流程应该是这样的:
auth-module
拦截请求,如果有效,代理将其传递给私有服务auth-module
应保留由 设置的标头并发送给客户端我想我没有正确理解如何组合auth_request_set
, proxy_set_header
, auth_request_set
,也可能是它们不适合这种情况。
有没有办法在 NGINX 中实现这一点?
Bac*_*ash 10
好的,我能够在headers_more
模块的帮助下做到这一点。
完整配置为:
location = /jwtverify {
internal;
proxy_pass http://auth-module:8080/auth/verify;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-URI $request_uri;
}
location /profile {
auth_request /jwtverify;
# this gets called right after auth_request returns.
# it reads http "authorization" header from upstream (= auth_request)
# and sets it to the variable $auth_header
# /sf/answers/2203989021/
auth_request_set $auth_header $upstream_http_authorization;
# this gets called right before sending response to client.
# it adds the previously set variable (= "authorization"
# header from auth_request) to the response
more_set_headers "Authorization: $auth_header";
proxy_pass http://private-profile:80;
}
Run Code Online (Sandbox Code Playgroud)
这就是我在没有自定义模块的情况下解决这个问题的方法:
location /auth {
internal;
proxy_pass http://localhost:3000/auth;
proxy_pass_request_body off;
proxy_set_header Content-Length "";
proxy_set_header X-Original-URI $request_uri;
proxy_set_header X-Original-Remote-Addr $remote_addr;
proxy_set_header X-Original-Host $host;
}
location /protected {
auth_request /auth;
auth_request_set $authentication_id $sent_http_x_authentication_id;
proxy_pass http://localhost:3000/protected;
proxy_set_header X-Original-URI $request_uri;
proxy_set_header X-Original-Remote-Addr $remote_addr;
proxy_set_header X-Original-Host $host;
proxy_set_header X-Authentication-Id: $authentication_id;
}
Run Code Online (Sandbox Code Playgroud)
/auth
端点包含响应标头。矿井套X-Authentication-Id
auth_request_set
根据响应标头设置变量/protected
请求的一部分 归档时间: |
|
查看次数: |
7695 次 |
最近记录: |