Summary

The OIDC auth spec states that when performing authentication if there is a token in the cache it should set the token on the connection. There, however, is no prose test in the spec to actually validate in drivers that this is always true.

Motivation

Who is the affected end user?

Driver users.

How does this affect the end user?

No prose test covers the case where a connection could potentially not have a token set.

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

Edge case

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

Drivers could potentially fail reauthentication due to the presence of the token equality check if the connection never has its token set. This becomes present when more than one connection is in the connection pool.

Is this issue urgent?

No

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Yes

Acceptance Criteria

Add a test to the OIDC prose tests that simulates reauthentication with more than one connection in the connection pool and reauthentication happens for all connections in the pool.