Uploaded image for project: 'C Driver'
  1. C Driver
  2. CDRIVER-4489

Implement OIDC SASL mechanism

    • Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • To Do
    • Implement OIDC SASL mechanism
    • 7
    • 12
    • 16
    • 100
    • Hide

      Engineer(s): Kyle Kloberdanz

      2024-07-19:

      Status update:


      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.
      Show
      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.
    • Hide

      DRIVERS-2912:

      Show
      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

      This ticket was split from DRIVERS-2415, please see that ticket for a detailed description.

            Assignee:
            Unassigned Unassigned
            Reporter:
            dbeng-pm-bot PM Bot
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              20 weeks, 4 days