You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/12/04 18:17:12 UTC

[jira] [Closed] (INFRA-8372) Fisheye commit links in JIRA do not work, asks to "Authenticate to see related commits" on a different server

     [ https://issues.apache.org/jira/browse/INFRA-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed INFRA-8372.
------------------------
    Resolution: Fixed

So Atlassian uses 3 legged auth for the commits area. This means that although Jira and Fisheye are connected through 2 legged auth, allowing the Development section so show a commits link, clicking on that link requires a 3rd level of auth -- from you the user.

2 options exist.

Create yourself an account at fisheye6.atlassian.com

or 

use a user of 'apache' with password the same.

Whichever you use, the auth token should last 1800 days.

There are no other options.

> Fisheye commit links in JIRA do not work, asks to "Authenticate to see related commits" on a different server
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: INFRA-8372
>                 URL: https://issues.apache.org/jira/browse/INFRA-8372
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Fisheye, JIRA
>            Reporter: Alexander Klimetschek
>            Assignee: Gavin
>
> When I want to see commits on an issue (for example SLING-3909), and click on the link in the Development panel on a Jira issue on the right, I get the dialog asking me to "Authenticate to see related commits. Please log in to approve this application".
> But this links to https://fisheye6.atlassian.com, a completely different server. I don't have a login for that site and my ASF jira login doesn't work there either.
> Are you supposed to register on that site with any user name? Does it have to be the same user name?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)