missing information when connected to Crowd

[Won Je Choi]

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

[Marcin Kempa]

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

[Won Je Choi]

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. 

[Won Je Choi]

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