Hi, A bit of update: As most of the people here can't see the full discussion, I report it here [1], not sure this mailing list will be able to display it correctly though. Well, it seems it is enough to create a FishEye account once asked, it worked for me (careful, I've been correctly redirected to FishEye after my account creation but it takes time to really apply it next time, I didn't know so I reset my password and then I've been asked to allow FishEye to use my Jira info, I said yes and everything has been fine then). Can one committer try to go to a JIRA with commits (eg. https://issues.apache.org/jira/browse/FLEX-34119), click on "commits" under "Development" then create a FishEye account when requested, confirm he can see FishEye, then logout, try click again on "commits" and confirm it works again ?
Thanks, Frédéric THOMAS [1]ActivityStatus changed to Waiting For CustomerToday 2:57 PMLATESTChristopher Parker [Atlassian]Today 2:57 PMHi Fred, Is it a viable option for you guys to create accounts for yourselves in FishEye? You can sign up for an account manually by selecting Log In and then Not a member? Signup for an account, then once you have authenticated with FishEye via JIRA this authentication will be in place until you decide to remove it.It will be the whole instance of https://issues.apache.org/jira/ as system wide admin rights are needed in order to configure applinks between two Atlassian instances.Kind Regards,ChrisStatus changed to Atlassian InvestigatingToday 11:55 AMFrédéric THOMASToday 11:55 AMHi Chris, > Can you confirm whether the logged in JIRA users who are having trouble > accessing the FishEye commits have accounts in FishEye?AFAIK, we (JIRA users) > haven't got any FishEye accounts, we are only linked to the public instance, > the reason why we can't login I guess.> The service owner has specified that > if you are happy to give temporary admin rights on > https://issues.apache.org/jira/ then he can reconfigure the application > linkWhat is the Apache account we need to give temporary admin rights > ?Regards, -FredStatus changed to Waiting For CustomerToday 9:43 AMChristopher Parker [Atlassian]Today 9:43 AMHi Fred, The service owner has specified that if you are happy to give temporary admin rights on https://issues.apache.org/jira/ then he can reconfigure the application link - he has suggested he could remove the OAuth authentication in FishEye (incoming authentication) and leave anonymous access only. Applinks would continue to work as expected, JIRA will be making anonymous requests to FishEye and would retrieve all requested information without prompt for authentication. This has been tested locally and has been confirmed that it works this way - the only problem is that admin permissions will needed on both JIRA and FishEye in order for this to be implemented.As it is currently once https://issues.apache.org/jira/ users authenticate in FishEye (they can easily sign up for account there and create accounts for themselves) the authentication would persist, so they wouldn't need to authenticate each time they click on the commit details. This authentication can be removed at any moment by going to the Profile Settings/Authorised Applications within FishEye. Can you confirm whether the logged in JIRA users who are having trouble accessing the FishEye commits have accounts in FishEye?Kind Regards,ChrisChristopher Parker [Atlassian]Yesterday 1:55 PMHi Fred, I've relayed your response to the Service Owner for your instance, this is being dealt with via an internal ticket we have raised for this case.I will provide you with an update shortly.Kind Regards,ChrisStatus changed to Atlassian InvestigatingYesterday 10:29 AMFrédéric THOMASYesterday 10:29 AMHi Christopher, Happy new year.> Is this above process the one you were following when you are redirected to the URL you mentioned in the description?Yes, it is and more precisely, the "Authenticate to see related commits" message and link comes only if we are already logged in Jira with our Apache account, not as anonymous which works well.The issue is we can't access the FishEye details panel while logged in Jira.> if you are happy to do so the app links can be reconfigured for Anonymous access?Given that anonymous can already access the FishEye details panel, am I wrong to guess it is already configured that way ?What we need is to be able to access the FishEye details panel shown in the screenshot you uploaded even once logged in Jira, is that possible ?Regards, -FredStatus changed to Waiting For CustomerYesterday 9:27 AMChristopher Parker [Atlassian]Yesterday 9:27 AMHi Fred, Apologies for the delay in response.The service owner for your instance has looked into the issue and had the following comments to make;When you follow the link within JIRA on the development panel to display the FishEye information you are prompted with "Authenticate to see related commits" - once clicked you should be prompted to authenticate with fisheye6 on your behalf with read/write access. As can be seen in the below screenshot once this authentication process has been completed displaying the FishEye details works fine; Is this above process the one you were following when you are redirected to the URL you mentioned in the description?It was also pointed out that as fisheye6.atlassian.com is already a public instance visible to all if you are happy to do so the app links can be reconfigured for Anonymous access? Would this be a solution that could work for you?Kind Regards,ChrisChristopher Parker [Atlassian]Tuesday 9:19 AMHi Fred, Just to keep you updated this has been picked up and is being investigated by the service owner for your instance, we will hopefully update you shortly.Kind Regards,ChrisStatus changed to Frozen24/Dec/14 8:54 AMChristopher Parker [Atlassian]24/Dec/14 8:54 AMThanks Fred, I'll proceed to freeze this issue now, you can unfreeze it by adding a comment. I will update you with any progress that is made on the internal ticket.Kind Regards,ChrisFrédéric THOMAS23/Dec/14 6:37 PMSure Christopher, thanks for your time. -FredChristopher Parker [Atlassian]23/Dec/14 5:49 PMHi Fred, Apologies for the confusion, I have spoken to my colleagues and now fully understand your request I have created an internal ticket for this to be looked into and will keep you posted on any updates made.May I proceed to freeze this case while we wait for a response in the mean time?Kind Regards,ChrisFrédéric THOMAS23/Dec/14 5:02 PMApparently I forgot to paste the link [1] https://support.atlassian.com/servicedesk/customer/portal/18/FSH-11323Status changed to Atlassian Investigating23/Dec/14 4:47 PMFrédéric THOMAS23/Dec/14 4:47 PMHi Christopher, I hope you're well.Maybe my informations are not up to date but I always thought Atlassian was managing our public FishEye instance and we never had an admin access to it, I was the one who asked for having our Jira links to FishEye [1] and no one at the time provided me with such informations, could you please check the current status and eventually tell me how I can have access to the FishEye Administration menu ?Status changed to Waiting For Customer23/Dec/14 1:23 PMChristopher Parker [Atlassian]23/Dec/14 1:23 PMHi Fred, Thanks for contacting Atlassian Support and apologies for the delay in response.So we can investigate this further could you provide us with a Debug support.zip from FishEye, to do this;1. Go to FishEye Administration > Global Settings > Server > Debug Logging and click the Turn Debugging ON button. 2. Reproduce the problem. 3. Generate a Support Zip (FishEye Administration >> Systems Settings >> Atlassian Support Tools >> Support Zip). 4. Attach it to this ticket. 5. Go to FishEye Administration > Global Settings > Server > Debug Logging and click the Turn Debugging OFF button.Few questions around this;Are you using a proxy/reverse proxy?Are FishEye and JIRA hosted on different servers?What is the current set up of your application links between the 2 tools?Kind Regards,ChrisDetails22/Dec/14 10:51 AMPlease add any details that might help us help you.Hi, I'm part of the Apache Flex PMC project members and wanted to report that once logged in Jira we can't access the FishEye commits links any more, we have a popup saying "Authenticate to see related commits" with a link tohttps://fisheye6.atlassian.com/login?origUrl=https%3A%2F%2Ffisheye6.atlassian.com%2Fplugins%2Fservlet%2Foauth%2Fauthorize%3Foauth_callback%3Dhttps%253A%252F%252Fissues.apache.org%252Fjira%252Fplugins%252Fservlet%252Fapplinks%252Foauth%252Flogin-dance%252Faccess%253FapplicationLinkID%253Da9fc3fc2-6193-3801-b0c9-b7fb89335217%26oauth_token%3DxBO4YZJO7IN5VZfpuziy3mKBRCVphEJPWe would like this to work for even authenticated users, can you help ?Thanks, -FredSeverityLevel 3Affects Version/sUnknownCustomer TimezoneGMT+1 > From: [email protected] > To: [email protected] > Subject: RE: Re : Re: FishEye accounts > Date: Mon, 22 Dec 2014 09:54:56 +0000 > > Hi, > > I can confirm and I reported the behaviour [1] today, will keep you in touch > as soon as I have any answer. > > Thanks, > Frédéric THOMAS > > [1] https://support.atlassian.com/servicedesk/customer/portal/18/FSH-15797 > > > Date: Sat, 20 Dec 2014 11:59:05 +0100 > > Subject: Re : Re: FishEye accounts > > From: [email protected] > > To: [email protected] > > > > Actually that's Atlassian, will ask them tomorrow if no one do it before, > > Im amost in the plane right now > > > > --- Message initial --- > > > > De : "Alex Harui" <[email protected]> > > Envoyé : 20 décembre 2014 08:35 > > A : [email protected] > > Objet : Re: FishEye accounts > > > > Interesting. I can reproduce your problem by logging in. Is INFRA > > responsible for FishEye? > > > > -Alex > > > > On 12/19/14, 11:42 AM, "Mihai Chira" <[email protected]> wrote: > > > > >> I went to a couple of JIRA issues that had “1 commit” links and they > > >> worked for me. Is that what isn’t working for you? > > >Yes, that's the one I referred to. I remember they worked for me too > > >for a while, which is why I now noticed, as it felt like a regression. > > >Is it working for you for all tickets? > > > > > >> Did you try a different browser? > > >Wow, thanks for the suggestion. It's not the browser in the end, but > > >by testing in another one I noticed that I can see the commits by > > >clicking on that link *only when I'm signed out* of Jira. > > > > > >Could you guys please click on that link when you're logged into Jira > > >and another time when you're not? Thanks. > > >
