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

Jira and Confluence authentication and SSO

We are in the process of spinning up a service desk, and looking to utilize Confluence as the knowledgebase (KB) add in.  Our current setup is JIRA is integrated with our Active Directory and also serves as our user repository for Confluence.  

When a user is entering an issue from the customer portal, it searches and presents results pulled from Confluence which works great, the problem that we are trying to solve is when a user clicks on one of these results it then prompts for credentials even though both are using the JIRA user repositofy.  What is the best way to prevent the user from having to authenticate into Confluence to view the KB info?

I know "Crowd" can offer a solution, I would prefer not to license and maintain another product just to meet this single need.  I feel I may be missing something with the Application links and the associated authentication configuration as a potential solution.

2 answers

0 votes
Steven Behnke
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 12, 2015

If you want Single-Sign On, the Atlassian solution is a single directory within Crowd and using the Crowd-Seraph SSO Plugin in each client application.

0 votes
GabrielleJ
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 12, 2015

Yes, the "Application Links" is the way to go. I always wanted the "Trusted Application" links (which will not require any authentication prompt ever and that means these 2 applications fully trust each other) or you can use OAuth (which will require them to log-in one time). Using the former requires that JIRA and Confluence have the same set of users, if not you can only use OAuth.

 

https://confluence.atlassian.com/doc/integrating-jira-and-confluence-2825.html

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events