-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Authentication
-
None
Summary
We are switching to use launched Atlas clusters instead of shared Atlas clusters for OIDC testing.
Motivation
We cannot used shared Atlas clusters for OIDC testing, since even if we use appName, there can be only one configured failCommand on a server at a time.
Switching to launched Atlas clusters means that we have to adapt to the Atlas UI methods of configuring OIDC auth, which unfortunately affects how we run our tests.
Acceptance Criteria
Drivers can launch Atlas clusters using a script and run the test suite from all three supported platforms.
- is depended on by
-
RUST-1664 Implement OIDC SASL prose tests
- Closed
-
DRIVERS-2672 OIDC: Implement Machine Callback Mechanism
- Implementing
-
DRIVERS-2856 Rename OIDC property "PROVIDER_NAME" and config values
- Implementing
-
DRIVERS-2601 OIDC: Automatic token acquisition for GCP Identity Provider
- Implementing
- split to
-
CDRIVER-5518 OIDC Atlas Testing Updates
- Backlog
-
CXX-2996 OIDC Atlas Testing Updates
- Backlog
-
PHPLIB-1423 OIDC Atlas Testing Updates
- Backlog
-
RUBY-3430 OIDC Atlas Testing Updates
- Backlog
-
CSHARP-5019 OIDC Atlas Testing Updates
- Closed
-
GODRIVER-3170 OIDC Atlas Testing Updates
- Closed
-
JAVA-5395 OIDC Atlas Testing Updates
- Closed
-
MOTOR-1289 OIDC Atlas Testing Updates
- Closed
-
NODE-6058 OIDC Atlas Testing Updates
- Closed
-
PYTHON-4309 OIDC Atlas Testing Updates
- Closed
-
RUST-1898 OIDC Atlas Testing Updates
- Closed