Gadget Login and Approve button

I configured OAuth between 2 Jira instances. In one I placed a Activity Stream gadget from the other instance.

The first time I had to click a button "Login and Approve" in order to actually see the activity from the other site.

But every 10 minutes or so that button reappears again. I noticed in the browser's Java Console (Firebug) a message:

Security tokens will be refreshed every 720000ms

That's 12 minutes and this explain why the button reappears.

Is it possible to disable this setting???

Thank you!

1 answer

1 accepted

0 votes
Ahmad Danial Atlassian Team May 01, 2013

Hey there, Adolfo.

Have you tried to reproduce the problem in other Atlassian Supported Browsers (https://confluence.atlassian.com/display/JIRA/Supported+Platforms)? Have you configured your JIRA to run behind proxy? If yes, please try to remove the configuration and try to reproduce the problem again.

In addition to that, have you tried to enable Safe Mode to see (only if) it is related to any other third-party plugins in your instance and try to check if the issue is still there?

Warm regards,

Danial

This is what I am getting in the log:

WARN  [org.apache.http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2FXXX.XX.XX.XXX%3A8080%2Fjira", oauth_problem="token_rejected"}

XXX.XX.XX.XXX is the IP of the "producer", which is not behind a proxy.

I also get

WARN  [org.apache.http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2FXXX.XX.XX.XXX%3A8080%2Fjira", oauth_problem="permission_unknown"}

After login, the gadget shows correctly, but after a while the Login and Approve button shows again.

If I connect to the Jira at the producer, with the same user used to Allow the connection, and go to access-tokens under its Profile, I see a long list of messages like this:

JIRA expires in 29 days
Atlassian JIRA at null
Revoke Access - approved on May 2, 2013 at 4:00 PM - Read and Write Access

Apparentlly it did was a proxy between these 2 servers, after some changes with the settings I am not getting this error anymore.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,802 views 11 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot