2-legged OAuth is not properly configured on the remote stash end

This is the error I get when I try to create a trigger.  However, testing OAuth config on Ingoing/Outgoing on Stash and JIRA says it is configured correctly.

4 answers

having the same issue today. Anyone have any ideas? I have the IP addresses wildcarded on both ends...

I had to remove the existing applications links and re-create them to get this to work. Our problem started after upgrades to both JIRA and Stash. Apparently the newer versions have new features on the application links.

Same problem Here!

I am Also Having the same problem here

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 ...

3,198 views 13 19
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