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,464,351
Community Members
 
Community Events
176
Community Groups

missing information when connected to Crowd

We were using JIRA and Confluence connected to internal directory for years, and recently installed Crowd to use Azure SSO. When the directory is switched to Crowd, our users statistics in details get reset and I am afraid that any attributes such as filters, links, and etc created by specific users may get broken. If we switch back to internal directory, of course we get all the information about users back. Therefore, was wondering if there is any way for us to retrieve all those information, when connected to Crowd directory?

 

Thanks

1 answer

0 votes
Marcin Kempa Atlassian Team Jan 04, 2018

Hi @Won Je Choi!

 

When you mention 'users statistics' you mean login details such as login count and last login time?

What do you mean by attributes and links? are you referring to issue filters, comments created by users?

As those elements are mapped to the user by username, switching directories should not be a problem and still the users should have access to the entities they created (issues, comments, filters) - as long as the usernames in both directories match.

You also mentioned that you've adopted Crowd to make use of Azure SSO, are you using Office365 as a SAML identity provider? Do you use native Azure integration in Crowd or do you use third party addon?

At the moment Crowd does not support SAML SSO that comes from Azure, you may synchronize users from Azure AD and then configure Crowd SSO between Crowd, Jira and Confluence.

For the Data Center offering you may use native SAML SSO integration in Jira Data Center and Confluence Data Center to integrate with Azure SSO.

 

Marcin Kempa

Hi @Marcin Kempa

Thanks for the reply!

When you mention 'users statistics' you mean login details such as login count and last login time? What do you mean by attributes and links? are you referring to issue filters, comments created by users?

As those elements are mapped to the user by username, switching directories should not be a problem and still the users should have access to the entities they created (issues, comments, filters) - as long as the usernames in both directories match.

- Yes and yes, I see.. but is it possible to have Crowd to use the database that the internal directory was using? so all the data is matched as it was before?

You also mentioned that you've adopted Crowd to make use of Azure SSO, are you using Office365 as a SAML identity provider? Do you use native Azure integration in Crowd or do you use third party addon?

At the moment Crowd does not support SAML SSO that comes from Azure, you may synchronize users from Azure AD and then configure Crowd SSO between Crowd, Jira and Confluence.

For the Data Center offering you may use native SAML SSO integration in Jira Data Center and Confluence Data Center to integrate with Azure SSO.

- We use native Azure AD integration in Crowd, not using third party addon. And have integrated it to JIRA and Confluence, which are servers in our AWS environment, and we are able to login with o365 login credentials, but was wondering if we can have Crowd using the previous db. 

@Marcin Kempa Also, is there a document where that has this info, "As those elements are mapped to the user by username, switching directories should not be a problem and still the users should have access to the entities they created (issues, comments, filters) - as long as the usernames in both directories match."

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events