Skip to content

feat: migrate Azure DevOps auth to OAuth 2.0 with PKCE#19

Open
thealternator89 wants to merge 2 commits intomainfrom
feature/oauth2-devops
Open

feat: migrate Azure DevOps auth to OAuth 2.0 with PKCE#19
thealternator89 wants to merge 2 commits intomainfrom
feature/oauth2-devops

Conversation

@thealternator89
Copy link
Copy Markdown
Owner

Adds OAuth2.0 with PKCE for Azure DevOps integration to remove the need for PATs

Resolves #13

# Conflicts:
#	src/main/index.ts
#	src/main/services/azureDevOpsService.ts
#	src/renderer/pages/Settings.tsx
@thealternator89
Copy link
Copy Markdown
Owner Author

Note that merging this will prevent access until the Stitch application is approved in any tenant for Azure DevOps using the app (since we've removed the PAT option).

Plan for merging;

  • Launch the app, attempt to log in
  • Request approval for the Stitch app in the tenant

Assuming it works as expected (at least the initial login works, and closing/reopening the app doesn't require a new login), we can merge it.

Presumably the approval for the app registration in the tenant will persist even if the app isn't handling the token correctly, so we can fix it under this PR before merging without needing to request more assistance from the Infra team.

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.

OAuth 2.0 with PKCE for Azure DevOps

1 participant