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.

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

Auth - Support for Azure AD OBO (On Behalf Of) OAuth Token Integration #79359

Open
Angelodaniel opened this issue Oct 18, 2024 · 3 comments
Open
Labels
Component: Auth Sync: Jira Apply to auto-create a Jira shadow ticket

Comments

@Angelodaniel
Copy link
Member

Angelodaniel commented Oct 18, 2024

Problem Statement

Our team is integrating Azure with Sentry, but due to security policies, we are unable to use standard OAuth authentication. Instead, we are leveraging the On Behalf Of (OBO) OAuth token flow provided by Azure AD to authenticate users and access resources. However, Sentry currently does not support this flow natively, requiring custom workarounds on our side. We are requesting native support for the Azure OBO flow to enable smoother integration between Azure AD and Sentry.

Solution Brainstorm

No response

Product Area

Settings - Integrations

┆Issue is synchronized with this Jira Improvement by Unito

@Angelodaniel Angelodaniel changed the title Integrations - Support for Azure AD OBO (On Behalf Of) OAuth Token Integration Auth - Support for Azure AD OBO (On Behalf Of) OAuth Token Integration Oct 18, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Oct 18, 2024

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

@Angelodaniel
Copy link
Member Author

@leedongwei
Copy link
Member

Unfortunately, it doesn't seem to be a common use case.

We will not prioritize this feature request unless there's more demand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Auth Sync: Jira Apply to auto-create a Jira shadow ticket
Projects
Status: No status
Development

No branches or pull requests

2 participants