Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) #30525

Open
billwert opened this issue Aug 16, 2022 · 5 comments
Open

Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) #30525

billwert opened this issue Aug 16, 2022 · 5 comments
Assignees
@scottaddie
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Milestone
2025-03

Comments

@billwert
Copy link
Contributor

billwert commented Aug 16, 2022 •
edited by joshfree
Loading

VisualStudioCodeCredential will depend on a new authentication tool which replaces the Azure Account extension in Visual Studio Code. This tool is not yet built; more details to come. [https://github.com/microsoft/vscode/issues/178740]

Reminder: when added back to DAC, the default failure mode should be CredentialUnavailableException, as with other dev credentials in the chain.
@billwert billwert added Client This issue points to a problem in the data-plane of the library. Azure.Identity labels Aug 16, 2022
@billwert billwert added this to the Backlog milestone Aug 16, 2022
@schaabs schaabs mentioned this issue Oct 12, 2022
Merged
@KarishmaGhiya KarishmaGhiya mentioned this issue Dec 7, 2022
Closed
@joshfree joshfree moved this from Planned to Blocked in Azure Identity SDK Improvements Jan 18, 2023
@christothes christothes mentioned this issue Mar 8, 2023
Closed
@Kiechlus
Copy link

Kiechlus commented Jun 2, 2023

Is there a timeline on this?

@afscrome afscrome mentioned this issue Aug 10, 2023
Merged
schaabs pushed a commit that referenced this issue Aug 11, 2023
@afscrome
Update README.md (#38135)
f738f6a 
Issue #27263 has been closed, supersceeded by #30525.
A user could read #27263 begin closed as meaning the known issue is resolved.
Pointing the link directly to the current issue to avoid any confusion.
@joshfree joshfree changed the title New VisualStudioCodeCredential authentication Investigate: New VisualStudioCodeCredential authentication Aug 17, 2023
@joshfree joshfree moved this from Blocked to In Progress in Azure Identity SDK Improvements Aug 17, 2023
@joshfree joshfree modified the milestones: Backlog, 2023-11, 2023-10 Aug 17, 2023
@joshfree joshfree changed the title Investigate: New VisualStudioCodeCredential authentication Long Lead Investigate: New VisualStudioCodeCredential authentication Sep 11, 2023
@joshfree joshfree changed the title Long Lead Investigate: New VisualStudioCodeCredential authentication Long Lead Investigation: New VisualStudioCodeCredential authentication Sep 11, 2023
@jsquire jsquire modified the milestones: 2023-10, 2023-11 Oct 19, 2023
@joshfree joshfree assigned chlowell and unassigned schaabs Nov 6, 2023
@joshfree joshfree removed this from the 2023-11 milestone Nov 6, 2023
@alex-frankel alex-frankel mentioned this issue Dec 7, 2023
Closed
@cataggar cataggar mentioned this issue Dec 27, 2023
Closed
@joshfree joshfree changed the title Long Lead Investigation: New VisualStudioCodeCredential authentication Tracking SSO investigation Jan 8, 2024
@RickWinter RickWinter added this to the Backlog milestone Mar 6, 2024
@github-actions GitHub Actions
Copy link

Hi @billwert, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 16, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Azure Identity SDK Improvements Aug 16, 2024
@christothes christothes reopened this Aug 28, 2024
@joshfree joshfree changed the title Tracking SSO investigation Tracking: Re-enable VisualStudioCodeCredential after VSCode adopts BrokeredAuthentication (WAM) Oct 16, 2024
@joshfree joshfree moved this from Untriaged to Blocked in Azure Identity SDK Improvements Oct 16, 2024
@joshfree
Copy link
Member

@scottaddie could you add a link to the VSCode MSAL/WAM github issue

@joshfree joshfree moved this from Blocked to In Progress in Azure Identity SDK Improvements Oct 16, 2024
@joshfree joshfree moved this from In Progress to Blocked in Azure Identity SDK Improvements Oct 16, 2024
@joshfree joshfree modified the milestones: Backlog, 2025-03 Oct 16, 2024
@joshfree
Copy link
Member

Related: microsoft/vscode#178740

@joshfree joshfree modified the milestones: 2025-03, 2025-02 Oct 16, 2024
@joshfree joshfree changed the title Tracking: Re-enable VisualStudioCodeCredential after VSCode adopts BrokeredAuthentication (WAM) Tracking: Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) Oct 23, 2024
@joshfree joshfree changed the title Tracking: Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) Re-enable VisualStudioCodeCredential for Windows after VSCode adopts BrokeredAuthentication (WAM) Oct 23, 2024
@joshfree
Copy link
Member

Scoping this to Windows-only initially

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@scottaddie scottaddie

Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Projects
Azure Identity SDK Improvements
Status: Blocked
Milestone
2025-03
Development

No branches or pull requests
9 participants
@jsquire @christothes @joshfree @RickWinter @billwert @Kiechlus @scottaddie @chlowell @schaabs