-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Authentication
-
None
-
Needed - No Spec Changes
Summary
The auth spec says:
Drivers MUST immediately attempt a reauthentication on the connection using suitable credentials... This attempt MUST be irrespective of whether the operation is considered retryable.
Currently, the OIDC reauthentication tests only use times: 1 failpoints, so they never send a second 391 after a successful reauthentication. E.g. GODRIVER-3278
Motivation
Who is the affected end user?
OIDC users
How does this affect the end user?
If the server keeps returning 391 after a successful reauthentication, an affected driver hangs the operation and keeps fetching tokens from the identity provider until the operation's deadline (or forever with no deadline).
How likely is it that this problem or use case will occur?
Likely never since it needs a server that keeps rejecting the credential after accepting it in the SASL conversation.
If the problem does occur, what are the consequences and how severe are they?
The operation hangs and the identity provider is called repeatedly.
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
Yes
Acceptance Criteria
A unified test shows that when any authenticated command, using find and insert as representatives, gets 391 twice in a row (times: 2), the driver reauthenticates and retries once, then raises the second 391 to the user, with exactly two command started events.
- is related to
-
GODRIVER-4221 Operation.Execute retries indefinitely on repeated ReauthenticationRequired (391) after a successful reauthentication
-
- Backlog
-