[DRIVERS-2673] OIDC: Implement Machine Callback Mechanism Created: 13/Jul/23  Updated: 25/Jul/23  Resolved: 13/Jul/23

Status: Closed
Project: Drivers
Component/s: Authentication
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Steve Silvester Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Implement OIDC SASL mechanism
Driver Changes: Needed
Server Compat: 7.0
Quarter: FY23Q4, FY24Q1, FY24Q2

 Description   

Summary

As part of https://jira.mongodb.org/browse/CLOUDP-178758, we will need to provide callbacks for machine interaction (Milestone A.3). This is a separate API from the one originally implemented in DRIVERS-2415, which was for human interaction (Milestone A.1).

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

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

Main path? Edge case?

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

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?


Generated at Thu Feb 08 08:26:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.