[jira] (MCHANGES-291) Cannot authenticate to Jira OnDemand
[
https://jira.codehaus.org/browse/MCHANGES-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=311164#comment-311164
]
Jamie Duncombe commented on MCHANGES-291:
-
Hi,
I am also seeing this problem on a Jira OnDemand instance. It started
occurring around Mid-September which is also when Atlassian updated the
authentication mechanisms for OnDemand instances.
I'm guessing it's related to the authentication no longer working as if I copy
the URL generated by the plugin and pasting it into a browser window which
already has a valid session on the Jira Instance the Url itself works fine.
Out of interest is there a particular reason you haven't switched to using the
REST api for jira? Is this just because it isn't turned on by default in all
Jira instances?
I also have a support request open with Atlassian on the issue, so if they are
able to provide me with any advice or information for fixing the issue I'll
provide it here.
Jamie
Cannot authenticate to Jira OnDemand
Key: MCHANGES-291
URL: https://jira.codehaus.org/browse/MCHANGES-291
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.8
Reporter: Gary Clayburg
This plugin recently stopped working for our project that uses Atlassian Jira
OnDemand.
It now appears to fail with this 400 error. I'm thinking this is due to
recent changes in the way that Jira OnDemand is doing authentication. I get a
similar error in a browser if the session is not authenticated. Does anyone
else use Jira OnDemand with this plugin?
{code}
$ mvn -f pom_changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.8:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Downloading from JIRA at:
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100reset=truejqlQuery=project+%3D+OIAM+AND+fixVersion+in+%28%221.0.5%22%29+AND+status+in+%28Closed%29+AND+resolution+in+%28Fixed%29+ORDER+BY+priority+DESC%2C+created+DESC
[WARNING] Downloading from JIRA failed. Received: [400]
[WARNING] JIRA file C:\QA\integration-tests\target\jira-results.xml doesn't
exist.
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 3.340s
[INFO] Finished at: Fri Oct 05 09:32:48 MDT 2012
[INFO] Final Memory: 18M/152M
[INFO]
{code}
The pom.xml file is this:
{code}
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.urlremoved/groupId
artifactIdchanges-tests/artifactId
packagingjar/packaging
namechanges-tests/name
version1.22/version
issueManagement
systemJIRA/system
urlhttps://urlremoved.jira.com/browse/OIAM/url
/issueManagement
build
finalNamechanges-tests/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.8/version
configuration
useJqltrue/useJql
fixVersionIds1.0.5/fixVersionIds
jiraUserjustsomed...@somewhere.com/jiraUser
jiraPasswordEnterRealPasswordHere/jiraPassword
/configuration
/plugin
/plugins
/build
reporting
plugins
/plugins
/reporting
dependencies
/dependencies
/project
{code}
I also notice that even this test is executed in debug mode, it indicates
that login to Jira succeeded even when an invalid password is supplied:
{code}
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[DEBUG] Encoding JQL query project = OIAM AND fixVersion in (1.0.5) AND
status in (Closed) AND resolution in (Fixed) ORDER BY priority DESC, created
DESC
[DEBUG] Encoded JQL query
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[
https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305617#comment-305617
]
Jamie Duncombe commented on MCHANGES-285:
-
I am also able to confirm that I'm seeing this problem using a Jira 5.1 hosted
by Atlassian OnDemand, project was previously working on Jira 4.1.3 download
edition.
Viewing the generated URL from my stack trace in a web browser I can confirm
that the page returned is not in XML format but is the html page without
decoration, in my case at least it does return the correct results for the JQL
query.
URL generated:
https://{jira instance address removed for
security}/secure/IssueNavigator.jspa?view=rsspid=10680statusIds=1statusIds=3statusIds=4statusIds=5statusIds=6resolutionIds=-1resolutionIds=1resolutionIds=2resolutionIds=3resolutionIds=4resolutionIds=5component=11750sorter/field=createdsorter/order=DESCsorter/field=prioritysorter/order=DESCtempMax=100reset=truedecorator=none
A working URL obtained by requesting the xml (rss 0.9.2) format from the above
page:
https://{jira instance address removed for
security}/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+TOOLS+AND+component+%3D+toolname+ORDER+BY+created+DESC%2C+priority+DESCtempMax=100
Hope this helps,
Jamie
SAXException parsing JIRA XML from JIRA 5.1
Key: MCHANGES-285
URL: https://jira.codehaus.org/browse/MCHANGES-285
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.7.1
Environment: osx rhel sun java 1.6.0_30
Reporter: Micah Whitacre
When trying to generate a changes report from a JIRA instance running 5.1[1]
I get the following exception
[INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1
Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[INFO] Downloading from JIRA at:
http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jamie Duncombe updated MCHANGES-285: Attachment: patch-2.7.x.txt Hi Gary, The error you are seeing is because you have applied the patch to the 2.7.1 tag source code (there have been changes in the trunk to how the annotations are specified which are not backward compatible with the 2.7.1 codebase). I'm attaching a slight variation of the patch to fix this issue. It will also update the pom to build a 2.7.2 version of the pom so you should update your client project to match this. Let me know if you run into any problems, Jamie SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at
