7 Commits

Author	SHA1	Message	Date
Chao Chen	83da5ff575	[3.4] Backport #12671 clientv3: Replace balancer with upstream grpc solution ... Signed-off-by: Chao Chen <chaochn@amazon.com>	2023-10-30 09:26:40 -07:00
yoyinzyc	03f79003d4	clientV3: simplify grpc dialer usage. Remove workaround #11184 after bumping grpc to 1.26.0. ... Signed-off-by: Chao Chen <chaochn@amazon.com>	2023-10-27 12:10:54 -07:00
CFC4N	0cf5a72c2a	credentials: let GetRequestMetadata() return nil when authToken isn't initialized. ... Signed-off-by: Chao Chen <chaochn@amazon.com>	2023-10-25 12:51:30 -07:00
Joe Betz	c454344f14	clientv3: Set authority used in cert checks to host of endpoint	2019-10-08 15:35:27 -07:00
Gyuho Lee	3dc00ab615	clientv3: move auth token credential to "credentials" package ... Signed-off-by: Gyuho Lee <leegyuho@amazon.com>	2019-07-26 09:17:44 -07:00
Gyuho Lee	db61ee106c	clientv3/credentials: set dial target "Authority" with target address ... Overwrite authority when it's IP. When user dials with "grpc.WithDialer", "grpc.DialContext" "cc.parsedTarget" update only happens once. This is problematic, because when TLS is enabled, retries happen through "grpc.WithDialer" with static "cc.parsedTarget" from the initial dial call. If the server authenticates by IP addresses, we want to set a new endpoint as a new authority. Otherwise "transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, 192.168.121.180, not 192.168.223.156" when the new dial target is "192.168.121.180" whose certificate host name is also "192.168.121.180" but client tries to authenticate with previously set "cc.parsedTarget" field "192.168.223.156" Signed-off-by: Gyuho Lee <leegyuho@amazon.com>	2019-07-26 09:17:40 -07:00
Gyuho Lee	324c876742	clientv3/credential: implement grpc/credentials.Bundle ... Signed-off-by: Gyuho Lee <leegyuho@amazon.com>	2019-07-26 08:56:05 -07:00