Every time the server running JIRA reboots, the 2-Legged OAuth requests need to be reenabled. If it's not, some of our plugins don't work and the Application Navigator at the upper left hand corner does not show up for JIRA.
How do I get the 2-Legged OAuth enabled every time the server reboots?
Hi Mike, how you doing? =)
Your query indeed makes totally sense.
However, there is an internal service (monitor) that already does that, see the error below from a failure process in retrieving an application link information:
2013-11-09 10:15:25,124 StreamsCompletionService::thread-9224 WARN admin com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl:activityProviderMonitor [atlassian.streams.internal.ActivityProviderConnectionMonitorImpl$ActivityMonitorJob] Could not reach provider Stash; it will be omitted from the stream. The connection will be retried in 5 minutes
So basically JIRA in this case will 'ping' Stash again in 5 minutes to see if it can establish an app link again. I believe it is the time it will take to find your application link again. Can you confirm? If we dig deeper I believe we can check for the occurrence of this 'ping' into the logs and determine on which frequency it will "renew" your connection.
Please let us know how it goes.
Looking forward to hear from you.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs