-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
overrideAuthority does not impact authority for JWT in jwt_token_creds #2682
Comments
ejona86
added a commit
to ejona86/grpc-java
that referenced
this issue
Feb 1, 2017
Commit 65e4d9f caused grpc/grpc#9497 and grpc#2680 (dup). It is believed to be because the JWT does not see the authority passed to overrideAuthority. So the changes to interop-testing client are temporarily reverted here. Note that this breaks GRPC_PROXY_EXP testing, so the incompatibility needs to be resolved. Solving grpc#2682 will allow reverting this change.
ejona86
added a commit
to ejona86/grpc-java
that referenced
this issue
Feb 1, 2017
Commit 65e4d9f broke the jwt_token_creds. It is believed to be because the JWT does not see the authority passed to overrideAuthority. So the changes to interop-testing client are temporarily reverted here. Note that this breaks GRPC_PROXY_EXP testing, so the incompatibility needs to be resolved. Solving grpc#2682 will allow reverting this change. Fixes grpc/grpc#9497 Fixes grpc#2680
ejona86
added a commit
that referenced
this issue
Feb 1, 2017
Commit 65e4d9f broke the jwt_token_creds. It is believed to be because the JWT does not see the authority passed to overrideAuthority. So the changes to interop-testing client are temporarily reverted here. Note that this breaks GRPC_PROXY_EXP testing, so the incompatibility needs to be resolved. Solving #2682 will allow reverting this change. Fixes grpc/grpc#9497 Fixes #2680
Root problem:
|
I believe this is broken independent of whether using |
zpencer
added a commit
that referenced
this issue
Apr 27, 2017
AbstractManagedChannelImplBuilder accepts an overrideAuthority parameter, but this value is not hooked up to the name resolver object. Ultimately, Channel.authority consults with the NameResolver, so the overrideAuthority should be hooked into the NameResolverFactory, while all other functionality should be preserved. Also, add unit tests for all the variants of OkHttpChannelBuilder and NettyChannelBuilder constructors, namely to test the slightly different NettyChannelBuilder(SocketAddress) code path. Fixes #2682
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
65e4d9f#diff-850c920bd69ac031d7e98cab9459dec8 caused grpc/grpc#9497
The text was updated successfully, but these errors were encountered: