Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,699
Community Members
 
Community Events
184
Community Groups

Scriptrunner: You do not have an authorized access token for the remote resource.

Deleted user Sep 28, 2017

Attempting to run it through the Script Runner console, what could the issue be?

Both JIRA and Confluence are linked to each other with oAuth(not impersonated), and both have green light for connectivity.

 

Full error:

 

com.atlassian.applinks.api.CredentialsRequiredException: You do not have an authorized access token for the remote resource. at com.atlassian.applinks.oauth.auth.ThreeLeggedOAuthRequestFactoryImpl.retrieveConsumerToken(ThreeLeggedOAuthRequestFactoryImpl.java:93) at com.atlassian.applinks.oauth.auth.ThreeLeggedOAuthRequestFactoryImpl.createRequest(ThreeLeggedOAuthRequestFactoryImpl.java:86) at com.atlassian.applinks.core.auth.ApplicationLinkRequestFactoryFactoryImpl$AbsoluteURLRequestFactory.createRequest(ApplicationLinkRequestFactoryFactoryImpl.java:180) at com.atlassian.applinks.api.ApplicationLinkRequestFactory$createRequest.call(Unknown Source) at Script3.run(Script3.groovy:64)

 

3 answers

using impersonation solved the issue for me.

Not sure what the technical fallout is - but if you need a quick fix.. ;)

It solved the issue for me too.  Thank you!

Can you tell us how did you do to use impersonation?

I figured out that it means to reconfigure the Application Link between Confluence and JIRA to use [OAuth with impersonation] instead.

Like Михаил К likes this
1 vote
Daniel Yelamos [Adaptavist]
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 Leaders.
Oct 03, 2017

Hi Christian.

I believe if you want to do a certain type of request, you must have OAuth for both inward and outward connections for JIRA and Confluence.

I recently "demoed" a use case with both Confluence and JIRA and I could only get it to work with that configuration. I was making a request to create a page. Which really makes sense. If you do not impersonate a user how do you make sure that the user has rights to perform the action that you want him to?

I might be wrong, since I haven't been in this rodeo for that long, but in my opinion, you should try your luck with the mirror OAuth config.

Cheers!

DYelamos

I am having this same issue. I am pretty sure I have OAuth for both inward and outward connections. jira-link.PNGconf-link.PNG

Oops, meant to reply to the answer above. But, were you able to resolve this somehow?

I resolved mine by changing the local authentication all from OAuth to OAuth with impersonation. 

It's also assumed that both JIRA and Confluence shared the same LDAP users

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events