We are using crowd (2.8) to enable SSO for Atlassian applications (Jira/Confluence/bamboo/stash), as well as some other DEVOPS apps. It is working correctly. However, when I log on to crowd as administrator and list active user sessions, it shows me all possible users with initialization and last accessed date as of now, (or sometime I have seen that within past 30 minutes). Is that typical behavior?
I don't see that behavior on any other environment, where we have not enabled SSO Atlassian applications ( although other DEVOPS apps are SSO enabled)
Will this have any performance impact? we are talking about 3k+ users, and will potentially add many more.
Thanks for response,
Literally all the users are listed as having active session. I am pretty sure all these users should not be there. It doesn't always happen, and trying to figure out what causes it, and what may be the performance impact on crowd.
We do use crowd to implement SSO for Atlassian products as well as other tools (Jenkins etc). we also user crowdid to enable SSO for SonarQube.
Is there anyway to get details of all these sessions, which may shed light how did they get created to begin with?
Any suggestions will be appreciated.
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 ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot