Issue Details (XML | Word | Printable)

Key: MPJIRA-8
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Carlos Sanchez
Reporter: Dr. Spock
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Maven 1.x JIRA Plugin

Authentication support for access a private Jira instalation

Created: 08/Jan/05 10:56 AM   Updated: 12/Aug/05 02:02 PM   Resolved: 12/Aug/05 02:02 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Time Tracking:
Not Specified

File Attachments: 1. GZip Archive jira.tar.gz (12 kB)
2. File MPJIRA-8.svn-diff (16 kB)

Issue Links:
Supercedes
 


 Description  « Hide

Add authentication support for access a restricted Jira instalation based on a password.



Dr. Spock added a comment - 08/Jan/05 11:04 AM

A modified version of jira plugin based on release 1.1.2 that support authentication to access a restricted jira instalation.
This version contains the following implemented features:

  • Authentication support for access a restricted jira instalation.
  • Web authentication support for restricted web site (like browser authentication).
  • Customized filter property to restrict result issues from jira.
  • Customized properties to define the url base of jira instalation and to define the project id.
  • New properties to support the above features.
  • All new properties well documented into plugin xdoc site.

Dr. Spock added a comment - 08/Jan/05 11:12 AM

The attached archive 'jira.tar.gz' contains all files obtained from cvs with modified files that implement this suggested improvement.


Felipe Leme added a comment - 11/Jan/05 08:37 PM

Here is a SVN diff.

I took a look on this patch and it looks fine to me, although I didn't apply the changes because I don't have access to a Jira system that would require the authentication.

– Felipe


Felipe Leme added a comment - 12/Jan/05 05:07 AM

Dr. Spock,

I tested it in a protected Jira and it works. I also changed some properties:

maven.jira.hostUser => maven.jira.auth.webUsername
maven.jira.hostPassword => maven.jira.auth.webPassword
maven.jira.user => maven.jira.auth.jiraUsername
maven.jira.password => maven.jira.auth.jiraUsername

But I'm still hesitant to apply the patch due to the projectId, url and filter properties - are they really necessary? Couldn't you use the information on the POM?

Generally speaking, we try to avoid adding new properties to the plugins, unless they are strictly necessary.

– Felipe


Carlos Sanchez added a comment - 12/Aug/05 02:02 PM

Fixed as part of MPJIRA-13