microsoft / microsoft/vscode-documentdb
Investigate driver support for OIDC connection-string handling across auth methods
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
This is exploratory follow-up from managed identity work. Investigate whether the MongoDB driver can own normalization/translation of OIDC connection-string options across Microsoft Entra ID and managed identity rather than each VS Code extension auth handler stripping/rebuilding options; identify other OIDC auth methods and their option contracts; preserve security constraints around callback/host configuration; reference #639 as a user-raised OIDC host-allowlist report. No implementation is proposed by this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the MongoDB driver’s OIDC connection-string handling with each VS Code extension authentication handler, including Microsoft Entra ID and managed identity. Review other OIDC methods and their option contracts, then check #639 for the host-allowlist concern. Done means documenting the contracts, security constraints, and whether normalization should move into the driver; no implementation is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, typescript, vscode
- Domain
- authentication, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100