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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Alternative for "basic auth" and "trusted applications" for application links


Since recent versions of the Atlassian application links library, the two authentication types "basic auth" and "trusted applications" are not available anymore. Instead, only OAuth and "OAuth impersonation" are supported.

Is there still a way to use one of the two mentioned removed authentication schemes with application links? E.g., what do you do when you want to link two Atlassian applications, but some users only have an account in one of them but you still want to allow them to access information of the other app where they don't have an account?



1 answer

1 accepted

0 votes
Answer accepted
Shaun S Atlassian Team Apr 05, 2018

Hi Michael,

The basic auth and trust application link types were removed in version 5.2 of the application link plugin. OAuth is the only authentication type that can be configured after this version. The recommended way to provide an unlicensed user access to a resource is to grant anonymous read-only/browse access to the project associated with that resource. I was able to find a comment in this feature request in which a user reported being able to configure legacy application link options by appending ?legacyEdit=true to the application link configuration page. Since the legacy authentication options are deprecated, your mileage may vary on whether this works or will work in the future though.  

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events