Support Internal/Public integrations with OAuth authentication for security purpose.

[palemmahesh]

Problem Statement

Internal Integrations we can give url with username and password to send events to another url. But it will be good to provide oAuth 2.0 setup for external/internal integrations for security purpose not to give clear text password in the url.

Solution Brainstorm

OAuth 2.0 support for internal integrations

Product Area

Settings - Auth

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[mdtro]

@palemmahesh - Can you provide further clarification and details of what you are referring to? In no scenario should you be providing a password in the URL.

Sentry's Internal Integration platform does support OAuth 2.0 authentication. It's not strictly required, as we do support just using token to authenticate, but you're also able to use OAuth 2.0's Client Credential Flow to receive a temporary access token.

You can find details about this in our documentation:

• https://docs.sentry.io/organization/integrations/integration-platform/internal-integration/
• https://docs.sentry.io/organization/integrations/integration-platform/public-integration/#oauth-process

[Christinarlong]

Closing as we have this, please make a follow up if this isn't the case.