getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.67k stars 4.15k forks source link

Azure DevOps Integration Problem: Allow use of service principals #78249

Open hauskens opened 20 hours ago

hauskens commented 20 hours ago

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Due to #77570 we will need to add the integration again, and doing so requires some additional permissions to be approved. This would normally not be a problem for most users, but organizations can put restrictions on this, which will result in below message:

Image

In my case i am not allowed to get these permissions on my own user, but i can get a App Registrations with these permissions. It is very common for applications to utilize existing service principals to authenticate by configuring a Client ID, Client Secret and Tenant ID.

I will not be able to connect our sentry environment with Azure Devops if i am not able to use an existing App Registrations to authenticate with due to the permissions that are requested on behalf of my user and my organizations policy.

Expected Result

Allow users to authenticate the integration with App Registrations

Actual Result

See above

Product Area

Settings - Integrations

Link

No response

DSN

No response

Version

No response

getsantry[bot] commented 20 hours ago

Auto-routing to @getsentry/product-owners-settings-integrations for triage ⏲️

sentaur-athena commented 15 hours ago

@hauskens https://github.com/getsentry/sentry/issues/77570 didn't change the permission requirements of the app. Were you able to install the previous sentry azure installation? or was this an issue with the previous version of our App too?