Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
Description
Summary
This would come after OIDC implementation and the purpose of this followup work is to hook into Azure so that OIDC works on that platform. This work is part of the Milestone A.3 of the OIDC initiative, for machine interaction.
Attachments
Issue Links
- depends on
-
DRIVERS-2600 Clean up Azure resources on task failure
-
- Closed
-
-
DRIVERS-2672 OIDC: Implement Machine Callback Mechanism
-
- Implementing
-
- has to be done after
-
DRIVERS-2415 Implement OIDC SASL mechanism
-
- Implementing
-
- is related to
-
DRIVERS-2415 Implement OIDC SASL mechanism
-
- Implementing
-
-
NODE-5761 Skip Azure OIDC tests
-
- Closed
-
- related to
-
DRIVERS-2601 OIDC: Automatic token acquisition for GCP Identity Provider
-
- Blocked
-
- split to
-
NODE-4929 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Backlog
-
-
CDRIVER-4548 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
CSHARP-4474 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
CXX-2630 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
GODRIVER-2728 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
JAVA-4834 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
PHPLIB-1059 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
RUBY-3201 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
RUST-1562 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Blocked
-
-
MOTOR-1078 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Closed
-
-
PYTHON-3467 OIDC: Automatic token acquisition for Azure Identity Provider
-
- Closed
-