Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,430
Community Members
 
Community Events
176
Community Groups

Unable to create jira tickets from Share point using Issue Collectors

Edited

Hi Team,

We upgraded jira instance from 8.201 to 8.20.4 as per the security Vulnerability. Users complained they were not able to create jira tickets from Share point using Issue Collectors.  Only upgrade and reindex was happened other than this we did not change anything.

We found this from logs.

2022-02-07 11:17:27,135 http-nio-8080-exec-77 url: /rest/collectors/1.0/template/custom/76e17b8b WARN anonymous 677x13633435x6 - 206.224.73.126,172.31.10.60 /rest/collectors/1.0/template/custom/76e17b8b [c.a.p.r.c.security.jersey.XsrfResourceFilter] XSRF checks failed for request: https://atlassian.spscommerce.com/rest/collectors/1.0/template/custom/76e17b8b , origin: https://atlassian.spscommerce.com , referrer: https://atlassian.spscommerce.com/rest/collectors/1.0/template/form/76e17b8b

Attached screenshot for your reference.

issue collectors.PNG

1 answer

Response from Atlassian Support.

Thank you for contacting Atlassian support, and our apologies for the delayed response.

I understand that Issue Collectors have been failing recently, since you upgraded to Jira 8.20.4.

I've had a look in the support zip (thank you for that!) and I see the following warnings:

2022-02-08 09:20:25,507 http-nio-8080-exec-171 url: /rest/collectors/1.0/template/custom/a294c527 WARN anonymous 560x15483482x3 - 124.123.190.220,172.31.10.60 /rest/collectors/1.0/template/custom/a294c527 [c.a.p.r.c.security.jersey.XsrfResourceFilter] XSRF checks failed for request: https://atlassian.spscommerce.com/rest/collectors/1.0/template/custom/a294c527 , origin: https://atlassian.spscommerce.com , referrer: https://atlassian.spscommerce.com/rest/collectors/1.0/template/form/a294c5272022-02-08 09:20:27,026 http-nio-8080-exec-108 url: /rest/collectors/1.0/template/custom/a294c527 WARN anonymous 560x15483525x5 - 124.123.190.220,172.31.10.60 /rest/collectors/1.0/template/custom/a294c527 [c.a.p.r.c.security.jersey.XsrfResourceFilter] XSRF checks failed for request: https://atlassian.spscommerce.com/rest/collectors/1.0/template/custom/a294c527 , origin: https://atlassian.spscommerce.com , referrer: https://atlassian.spscommerce.com/rest/collectors/1.0/template/form/a294c527

Given the timing of this, you seem to be affected by this bug:

Which is the result of a fix for another bug, done in Jira 8.20.3:

The workaround is to return Jira to its prior behaviour:

The following workaround will disable XSRF checks for the issue collector, which was the behaviour prior to JRASERVER-73068. This may be tolerable for you, but it's worthwhile confirming within your organisation

Modify the reverse proxy / load balancer / WAF to add the following header to the request as it makes it's way to the Jira node:

  • Condition: Method: POST
  • Condition: Request URL: /rest/collectors/1.0/template/custom/*
  • Action: Add header: X-Atlassian-Token: no-check

Please have a look and let me know if this helps, or if you have any questions about the above. Thank you, and have a good day ahead.

We have upgrade "JIRA Software server" version with 8.20.5 and still facing the same problem for "Issue Collectors"

Suggest an answer

Log in or Sign up to answer