Gary Clayburg created MCHANGES-291:
--------------------------------------

             Summary: 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=100&reset=true&jqlQuery=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";>
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.urlremoved</groupId>
    <artifactId>changes-tests</artifactId>
    <packaging>jar</packaging>
    <name>changes-tests</name>
    <version>1.22</version>
    <issueManagement>
        <system>JIRA</system>
        <url>https://urlremoved.jira.com/browse/OIAM</url>
    </issueManagement>
    <build>
        <finalName>changes-tests</finalName>

        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-changes-plugin</artifactId>
                <version>2.8</version>
                <configuration>
                    <useJql>true</useJql>
                    <fixVersionIds>1.0.5</fixVersionIds>
                    <jiraUser>justsomed...@somewhere.com</jiraUser>
                    <jiraPassword>EnterRealPasswordHere</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 
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
[DEBUG] JIRA lives at: https://urlremoved.jira.com
[DEBUG] Login URL: 
https://urlremoved.jira.com/login.jsp?os_destination=/secure/&os_username=justsomedude%40somewhere.com&os_password=*********************
[DEBUG] Successfully logged in into JIRA.
[DEBUG] download jira issues from url 
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=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
[INFO] Downloading from JIRA at: 
https://urlremoved.jira.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=100&reset=true&jqlQuery=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]
{code}


This issue is related to MCHANGES-285

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to