Summary

Per CSOT, authentication/handshake steps use the remaining computedServerSelectionTimeout, while only socket establishment uses min(connectTimeoutMS, remaining computedServerSelectionTimeout). The OIDC spec currently states the callback timeout as min(remaining connectTimeoutMS, remaining timeoutMS). Since the OIDC callback is part of authentication (not socket establishment), its timeout must be the remaining computedServerSelectionTimeout.

Motivation

Who is the affected end user?

Driver teams implementing the CSOT/OIDC spec (and indirectly, applications using those drivers).

How does this affect the end user?

Inconsistent/incorrect timeouts.

How likely is it that this problem or use case will occur?

Unlikely.

If the problem does occur, what are the consequences and how severe are they?

Moderate, potentially auth failures.

Is this issue urgent?

Not urgent, but important to prevent rollout inconsistencies.

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

No

Acceptance Criteria

OIDC spec updated to state: OIDC callback timeout = remaining computedServerSelectionTimeout when CSOT is enabled (no min with connectTimeoutMS).