Acting As

Garfio performs actions against the issue tracker acting as the user who makes the commit. In order to do that, a username and a password is needed. But, how is that possible if the user's password is never provided? Thanks to the "Acting As" patch installed in the issue tracker, the system is allowed to authenticate as if he were the user without compromising the issue tracker security. If this patch is not installed, every user's password should be provided to Garfio.

When the admnistrator creates a repository in the Garfio Web Application he/she provides three items:

• Service URL : The issue tracker service url (with the "Acting As" patch installed)
• Acting As Password : The password that Garfio will use to connect to the issue tracker.
• Description

Every time a user makes a commit, Garfio will try to authenticate against the issue tracker as if he were that user, providing his/her username and the Acting As password. Thanks to the installed patch, the issue tracker will accept this information and let Garfio do his job.

Mantis

We provide the patch for Mantis here (it has been proved for Mantisconnect version 0.0.6-svn-20060821 ). It is really simple to use, you just need to write the Acting As password in the following line before applying the patch:

if($p_password == "PASSWORD GOES HERE") 

and then provide that password when you create a repository in the Garfio Web Application.

Jira

There isn't a patch for Jira yet :( (we don't have a jira instance). Send us a patch!