search

getsentry / sentry

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

The Sentry JIRA application currently isn't loading within JIRA #18070

Closed MarkGabb-Alcumus closed 3 years ago

MarkGabb-Alcumus commented 4 years ago

Important Details

How are you running Sentry?

Cloud

Description

When I go to Configure the Sentry application in JIRA it doesn't respond. I get the following error message: App is not responding. Wait or cancel?

Steps to Reproduce

  1. Configure Sentry within JIRA.

Good items to include here include:

What you expected to happen

The Sentry app should be loading

Possible Solution

[If you have an idea on how this could be solved include that detail here.]

scefali commented 4 years ago

@markgarethgabb Thanks for writing in. Can you post a screenshot of the issue you see in Jira?

Dezeter commented 4 years ago

@markgarethgabb Thanks for writing in. Can you post a screenshot of the issue you see in Jira?

tmak commented 4 years ago

I'm having the same issue.

We're using an on-premise Sentry installation (9.1.1) with GitHub Authentication SSO enabled + JIRA Cloud.

I was able to get to the same step as Dezeter by following these instructions: https://forum.sentry.io/t/how-to-configure-jira-cloud-in-your-on-premise-sentry/6720

When I click on the Sign In to Sentry button it opens our Sentry dashboard in a new browser tab successfully. But that's it, nothing happens and JIRA is displaying App is not responding. Wait or cancel?.

joshInsta commented 4 years ago

Exact same issue. Our business has paid subscriptions for both sentry and jira and we can't get past App is not Responding

tbach commented 4 years ago

Exact same issue for me. I tried disabling all sorts of cookie restrictions since it mentions cross-site cookies, but no luck. This is a really unfortunate blocker since we're paying for both services and would really like to link them.

Dezeter commented 4 years ago

@scefali Is it possible to fix it?

DethAriel commented 3 years ago

The problem is this line of code (or at least this is one of the first problems):

        res["X-Frame-Options"] = "ALLOW-FROM %s" % self.request.GET["xdm_e"]

According to MDN here,

This is an obsolete directive that no longer works in modern browsers. Don't use it. [...] The Content-Security-Policy HTTP header has a frame-ancestors directive which you can use instead.

So I think the referenced line of code should instead be smth like this:

        res["Content-Security-Policy"] = "frame-ancestors %s" % self.request.GET["xdm_e"]
BYK commented 3 years ago

@DethAriel would you be willing to submit a PR since you seem to have identified some relevant code?

github-actions[bot] commented 3 years ago

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀