@@ -19,7 +19,7 @@ When the user uses the legacy provider sidecar configuration file with the new v
19
19
20
20
File changes:
21
21
22
- https://github.com/yahoojapan /authorization-proxy/pull/83/files
22
+ https://github.com/AthenZ /authorization-proxy/commit/79614ab05d4becffb48e1ed89f493a13b1f8791e
23
23
24
24
We have updated/changed the implementation in the following layers:
25
25
@@ -31,7 +31,7 @@ We have updated/changed the implementation in the following layers:
31
31
32
32
In this layer, we create gRPC handler and pass it to service layer.
33
33
34
- [ Reference] ( https://github.com/yahoojapan /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/usecase/authz_proxyd.go#L71-L84 )
34
+ [ Reference] ( https://github.com/AthenZ /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/usecase/authz_proxyd.go#L71-L84 )
35
35
36
36
#### Service layer
37
37
@@ -43,11 +43,11 @@ In this layer, we implemented gRPC reverse proxy handler.
43
43
44
44
When the value of the configuration ` proxy.scheme ` is set to ` grpc ` , the gRPC handler will be created, and the server will start with gRPC mode.
45
45
46
- [ Reference] ( https://github.com/yahoojapan /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/config/config.go#L133 )
46
+ [ Reference] ( https://github.com/AthenZ /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/config/config.go#L133 )
47
47
48
48
If it is not ` grpc ` , nil will be returned, and the service layer will start with HTTP mode.
49
49
50
- [ Reference] ( https://github.com/yahoojapan /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/handler/grpc.go )
50
+ [ Reference] ( https://github.com/AthenZ /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/handler/grpc.go )
51
51
52
52
It retrieves the role token from the gRPC metadata, and authorize it using the athenz-authorizer.
53
53
@@ -143,7 +143,7 @@ Due to the limitation of gRPC, each RPC endpoint support only 1 resource, a sepa
143
143
144
144
For the reasons above, currently Vald team decided to hardcode ` grpc ` in the action field and use the when performing authentication and authorization check.
145
145
146
- [ Reference] ( https://github.com/yahoojapan /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/handler/grpc.go#L67 )
146
+ [ Reference] ( https://github.com/AthenZ /authorization-proxy/blob/1e14186eb1dd959e246a18be98c92d40a677a56e/handler/grpc.go#L67 )
147
147
148
148
#### Policy Resources
149
149
0 commit comments