The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

OATH application link no longer available?

Alicia Pena
July 24, 2013

I cloned our 6.0 production jira onto a staging server VM and changed host settings, etc. But when I bring up staging jira to link it to staging fisheye there isn't an application link OATH option for incoming or outgoing. Only trusted or basic. How do I get the OATH option back so I can mimic productions setup for testing purposes?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
LucasA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 24, 2013

Hi Alicia,

I suggest you to perform the steps below on your staging JIRA system:

- Make a XML Backup (Administration -> Import & Export -> XML Backup);
- Remove the application link for the FishEye staging system;
- Stop JIRA;
- Delete all the content from the following tables on the JIRA database:

oauthconsumer
oauthconsumertoken
oauthspconsumer
oauthsptoken

Then, restart JIRA, stablish a new application link again.

Best regards,
Lucas Timm

Alicia Pena
July 25, 2013

Thank you Lucas. I tried all of that, truncating those db fields and restarting jira. However the OATH option is still missing. I'm wondering if there's a cert issue of somekind that could cause OATH not to be available. But I simply cloned the entire working production VM to create this staging VM so certs should be the same. Very strange.

TAGS
AUG Leaders

Atlassian Community Events