Skip to content

[3.4] clientv3: do not refresh token when users use CommonName based authentication#14792

Merged
ahrtr merged 3 commits intoetcd-io:release-3.4from
ahrtr:auth_3.4_20221117
Nov 17, 2022
Merged

[3.4] clientv3: do not refresh token when users use CommonName based authentication#14792
ahrtr merged 3 commits intoetcd-io:release-3.4from
ahrtr:auth_3.4_20221117

Conversation

@ahrtr
Copy link
Copy Markdown
Member

@ahrtr ahrtr commented Nov 17, 2022

Backport #14790 to 3.4.

PR for main: #14770

Issue: #14764

…tication

When users use the TLS CommonName based authentication, the
authTokenBundle is always nil. But it's possible for the clients
to get `rpctypes.ErrAuthOldRevision` response when the clients
concurrently modify auth data (e.g, addUser, deleteUser etc.).
In this case, there is no need to refresh the token; instead the
clients just need to retry the operations (e.g. Put, Delete etc).

Signed-off-by: Benjamin Wang <[email protected]>
@ahrtr ahrtr force-pushed the auth_3.4_20221117 branch from 18f0209 to 849e9ae Compare November 17, 2022 00:59
@ahrtr ahrtr force-pushed the auth_3.4_20221117 branch from 849e9ae to 90585e0 Compare November 17, 2022 01:12
@ahrtr
Copy link
Copy Markdown
Member Author

ahrtr commented Nov 17, 2022

cc @mitake @ptabor @serathius @spzala

@ahrtr ahrtr merged commit f4bf538 into etcd-io:release-3.4 Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants