Updating end-date to 2025-11-21 (no progress during off-site) What was accomplished since the last update? OIDC Azure integration in review. What goals are we targeting for the next two weeks? Merge OIDC Azure integration. Put GCP integration in review. Reasons for delays Paused during off-site.

2025-11-19 - 🔵 Done Updating end-date to 2025-11-21 (no progress during off-site) What was accomplished since the last update? OIDC Azure integration in review. What goals are we targeting for the next two weeks? Merge OIDC Azure integration. Put GCP integration in review. Reasons for delays Paused during off-site. 2025-10-30 - 🟡 Potential Risk Updating end-date to 2025-11-04 What was accomplished since the last update? OIDC machine callback merged. OIDC Azure integration working locally. Reported possible improvement to save round-trip on initial connections: DRIVERS-3319 What goals are we targeting for the next two weeks? Merge OIDC Azure integration. Start GCP integration. Reasons for delays Evergreen passing on Azure took some trial-and-error but working now. Some PTO and focused on some higher priority HELP tickets. 2025-10-23 - 🟡 Potential Risk Updating end-date to 2025-11-04 What was accomplished since the last update? OIDC machine callback merged. OIDC Azure integration working locally. Reported possible improvement to save round-trip on initial connections: DRIVERS-3319 What goals are we targeting for the next two weeks? Merge OIDC Azure integration. Start GCP integration. Reasons for delays Evergreen passing on Azure took some trial-and-error but working now. Some PTO and focused on some higher priority HELP tickets. 2025-10-23 - 🟡 Potential Risk 2025-10-09: Updating end-date to 2025-10-28 What was accomplished since the last update? OIDC cache merged. OIDC machine callback support nearing review. What goals are we targeting for the next two weeks? Get machine callback merged. Start on Azure callback. Reasons for delays More higher priority interruptions past two weeks (e.g. security bug CDRIVER-6112 motivated quick releases) 2025-10-13 - 🟡 Potential Risk 2025-10-09: Updating end-date to 2025-10-28 What was accomplished since the last update? OIDC cache merged. OIDC machine callback support nearing review. What goals are we targeting for the next two weeks? Get machine callback merged. Start on Azure callback. Reasons for delays More higher priority interruptions past two weeks (e.g. security bug CDRIVER-6112 motivated quick releases) 2025-09-26: No change to end-date. What was accomplished since the last update? OIDC cache in review. Getting OIDC machine callback support review-ready. What goals are we targeting for the next two weeks? Get machine callback merged. Start on Azure callback. 2025-09-11: Project resumed. Setting end-date to 2025-10-21 What was accomplished since the last update? Machine callback working locally. All prose tests passing. What goals are we targeting for the next two weeks? Get machine callback merged. Start on Azure callback. Reasons for delays Project started and stopped three previous times. Bottom-up estimate: 7 weeks. Description Tickets Estimate Machine callback CDRIVER-4698 3 week Azure CDRIVER-4548 1 week GCP CDRIVER-4611 1 week Tests CDRIVER-6022 1 week Docs CDRIVER-4579 + CDRIVER-6022 .5 week 2025-05-22: Pausing. Who actively worked on the project in the last two weeks? Micah (left MongoDB). What was accomplished since the last update? In-progress work pushed to a branch to be started again later. 2025-05-08: No change to end-date. What was accomplished since the last update? Environment validation and callback stubs merged. What goals are we targeting for the next two weeks? Integrate into Evergreen. Put in-progress work into a branch or patch. 2025-04-25: Setting end-date to 2025-05-30 What was accomplished since the last update? Project resumed. OIDC callback API merged. What goals are we targeting for the next two weeks? Get OIDC implementation (without human workflow) in review. Reasons for delays: Project was paused after Kyle left. Setting new start date (2025-04-14) Status update: Project resumed. OIDC callbacks API merged. Working on integrating into Evergreen. Engineer(s): Kyle Kloberdanz 2024-07-19: Status update: Progress pushed to branch: https://github.com/mongodb/mongo-c-driver/tree/CDRIVER-4689 Project is being paused. Engineer is leaving. Planning to restart later in FY25Q3. 2024-07-03: What was accomplished since the last update? Discovered a bug in the C driver where an expected Authentication failed error is logged by the driver, but the driver reports back a successful operation. This is the last issue that is blocking successful test completion. What goals are we targeting for the next two weeks? Plan to diagnose the cause of this bug and fix it in order to finish up the testing for this ticket. Are there any open dependencies that should be flagged for follow-up? Finishing this item depends on diagnosing and fixing the bug mentioned above. Are there any risks to the current project timeline? The risk is in being able to find the source of the bug mentioned above. 2024-06-20: Updated target end date to 2024-08-09 What was accomplished since the last update? Got all spec tests passing as well as discovered and successfully worked around a bug in the prose test description. Will be submitting a PR to update the prose test What goals are we targeting for the next two weeks? PR for OIDC callback should be up next week Automatic token acquisition for Azure Identity Provider Reasons for delays There was a server bug which Kyle was not aware of that was causing correct code to fail tests in Evergreen, so he had to resort to trial and error to attempt to get CI working. This was blocking progress since late April 2024-06-10: Updating end-date to 2024-06-28 What was accomplished since the last update? Debugging an issue where OIDC authorization has not been working on the server in CI, despite working locally. Kyle will reach out to Steve What goals are we targeting for the next two weeks? Complete implementation of Machine Callback Mechanism Start implementation of Azure Reasons for delays CI Issues, intern on-boarding, PTO 2024-05-24: Updating end-date to 2024-06-07 What was accomplished since the last update? Continued effort on integrating into Evergreen. What goals are we targeting for the next two weeks? Complete implementation of Machine Callback Mechanism. Start implementation of Azure. Reasons for delays Skunkworks. Got stuck investigating Evergreen task failures (scripts started mongo-orchestration twice). — 2024-05-10: Updating end-date to 2024-05-31 What was accomplished since the last update? Continued effort on integrating into Evergreen. What goals are we targeting for the next two weeks? Complete implementation of Machine Callback Mechanism. Start implementation of Azure. Reasons for delays Time spent on Debian + Docker packaging for C 1.27.0, 1.27.1, and libmongocrypt 1.10.0. Got Evergreen task failure due to config typo. Skunkworks. Engineer(s): Kyle Kloberdanz 2024-04-26: Updating end-date to 2024-05-17 What was accomplished since the last update? OIDC speculative auth working. Working on getting tests passing in Evergreen. What goals are we targeting for the next two weeks? Complete implementation of Machine Callback Mechanism. Start implementation of Azure. Reasons for delays Got stuck with speculative auth (was resolved). Resolving test failures in Evergreen. Engineer(s): Kyle Kloberdanz 2024-04-12: Setting end-date to 2024-05-03 What was accomplished since the last update? OIDC auth working locally with Machine Callback Mechanism What goals are we targeting for the next two weeks? Complete implementation of Machine Callback Mechanism. Start implementation of Azure.

DRIVERS-2912: Implement MONGODB-OIDC SASL support Add prose tests and unified spec tests Handle reauthentication for all auth types See example implementation in Python   Credentials are in this Doc