Skip to content

feat: interactive OAuth flow added #368

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.

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

aaudzei
Copy link
Contributor

@aaudzei aaudzei commented Jul 30, 2025

PR adds OAuth interactive authentication flow as a default token retrieval mechanism.
Original credentials flows are kept but need to be opted-in via command line args.

This is still WIP. ClientID needs to be replaced with a "ADO trusted" app once it is available.
Readme and Troubleshooting need to be updated as well.

GitHub issue number

Associated Risks

PR Checklist

  • I have read the contribution guidelines
  • I have read the code of conduct guidelines
  • Title of the pull request is clear and informative.
  • 👌 Code hygiene
  • 🔭 Telemetry added, updated, or N/A
  • 📄 Documentation added, updated, or N/A
  • 🛡️ Automated tests added, or N/A

🧪 How did you test it?

Manually via inspector, all authentication options

Copy link

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None


class OAuthAuthenticator {
static clientId = "ac9c72b1-86e4-4849-be22-eaae7731117a";
static authority = "https://login.microsoftonline.com/common";
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should use common only if user didn't provide any specific tenant and use that tenant instead - that would make it possible for guest users to use the MCP server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow Interactive Browser Authorization for Machines without Azure CLI
2 participants