Does anyone know what version of JIRA this will work with.
I have tried several different setting and I seem to always get this error.
2011-06-03 15:44:02 SEVERE [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] Unknown problem while raising issue in JIRA
I'm wondering if this has something to do with the token introduced in JIRA 4.1+
JIRA 4.1+ now uses form tokens as an additional level of security against cross-site request forgery.
Thanks,
Jeff
Answer by Jalpesh S. ·
Hi Team,
I have opened JIRA plugin.
Since this plugin gives value of incident .
I want to know which method is used in plugin to capture incident details.
Regards,
Jalpesh
Answer by Andreas G. ·
One of my colleagues just provided an updated version of our JIRA Action Plugin that will work with JIRA 5.2. Check it out if this might also be helpful for you: JIRA Action Plugin
Answer by deleted3919 ·
Hi Jeff,
this looks interesting, but I have not the possibility for downloading the package
com.atlassian.jira.security.xsrf.XsrfTokenGenerator.
I already asked my JIRA-admin, but she is a bit slow in things like this.
Do you know, where to download the package?
Regards
Jan
Jan,
You will need to talk with the JIRA admin. They should be able to pull this package from the JIRA install base.
The path would be similar to this,
/<install_path>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/security/xsrf
I found this class file,
SimpleXsrfTokenGenerator.class
Thanks,
Jeff
Answer by deleted3918 ·
Hello,
old thread, old problems.
I am trying to use the JIRA-Action-Plugin, but our JIRA (Version 5.1.5) needs a XSRF -Token to proceed the request and I have no idea how I can get it.
Has someone the same issue and already solved it?
Regards
Jan
The JIRA plugin was built to integrate with a previous version of JIRA that did not have the XSRF security token.
There is a setting in the JIRA configuration file to turn off the XSRF security token.
#jira.xsrf.enabled=true
You would need to set this to false,
jira.xsrf.enabled=false
However, I would not recommend this if this is an external facing JIRA application. If this is an internal JIRA application, then it would be acceptable to set this to false.
Please post if this is acceptable and helps with your issue. I also recall needing to change the URL in the plugin.
It might help if you could attach the log file for the plugin.
You can find this under the collector logs running the plugin.
Thanks,
Jeff
Hey Jeff,
thank you for your reply. I am still trying to convince our Jira-Admins, that we don't need the xsrf-token.
The log just throws this message.
SEVERE CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action Exception while raising issue in JIRA: java.net.ConnectException: Connection refused
The URL used generated in the plugin is the following.
When I put it in the browser, I just have to confirm the token-security-request to open a ticket. https://jira-test/secure/CreateIssueDetails.jspa?pid=10712&issuetype=145&priority=3&summary=SUMMARY&description=DESCRIPTIONreporter=REPORTER&assignee=ASSIGNEE&components=1&os_username=USERNAME&os_password=PASSWORD
Regards
Jan
link to JIRA support page,
https://developer.atlassian.com/display/JIRADEV/Form+Token+Handling
Answer by Jeffery Y. ·
ok, I'm looking at the code, and the URL create the issue is not what is used in the newer version of JIRA. I'm going to try and make our own version of the plugin.
Thanks,
Jeff
Thanks for your effort on this. When you have a new version let me know. We can post your version on the JIRA Plugin Download page
Answer by Andreas G. ·
Hi Jeffrey
best would be to contact the plugin owner. The owner is listed on the plugin download page
JANUARY 15, 3:00 PM GMT / 10:00 AM ET