Tunnel endpoint basic auth override

[filip-kis-fsc]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. use sentry tunnel with nextjs app
2. authenticate sentry via env variable
3. nextjs app has own basic auth unrelated to sentry
4. open app, type in basic auth credentials to login and observe network for sentry tunnel request

Expected Result

sentry tunnel request is successful

Actual Result

sentry tunnel request fails with status 400

causes: ["invalid project key"]
detail: "bad sentry DSN public key"

This appears to happen due to header 'authorization: Basic <xyz>' being sent to the tunnel endpoint. Note that this basic auth has nothing to do with sentry but the app itself.

Is there a way to avoid this override?

Sentry is already using SENTRY_AUTH_TOKEN env variable and has dsn specified in sentry.client.config.js, sentry.server.config.js and sentry.edge.config.js files.

Product Area

Other

Link

No response

DSN

https://00cd68d0276b4de3a6f342955581ac69@o430938.ingest.sentry.io/6122809

Version

7.55.0

[getsantry]

Assigning to @getsentry/support for routing, due by Thursday, June 15th at 5:00 pm (sfo). ⏲️

[getsantry]

Failed to route for Product Area: Other. Defaulting to @getsentry/open-source for triage, due by Tuesday, June 20th at 9:26 am (sea). ⏲️

[hubertdeng123]

Looks like the team that owns javascript SDK may be able to be of help here, transferring this over there.

[AbhiPrasad]

Hey @filip-kis-fsc, thanks for writing in. Are you using the tunnelRoute option to set up a tunnel? https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-tunneling-to-avoid-ad-blockers

If you enable the debug: true option in your sentry.client.config.js and sentry.server.config.js, what gets logged out?

Sentry.init({
  debug: true,
});