Thank you for the answer. But somehow we do not see all the sessions in the crowd. For example, when I see over 300 user sessions in JIRA, I got only 2 user sessions in Crowd, for JIRA/Crowd shared user directory. Also I tried to expire the session of that user, and he wasn't logged out by reloading the page. While expiring the user of Crowd internal directory expiring his session when reloads the browser page with Crowd admin panel opened.
Could you give a hint on that? Thank you.
Okay, that doesn't necessarily make it clear to me that you've got SSO enabled (login once to access all those apps), only that you have a shared userbase (the same credentials work on all those apps). If SSO isn't enabled, then Crowd won't know about sessions. If you do have SSO enabled, then I suspect that JIRA is doing some caching on its side. I suggest you raise a support request to figure out exactly what's going on if this is important to you, because this answers platform is not well suited to discussion and troubleshooting :)
I thought that SSO is one login among all the applications connected to shared CROWD's directory. I just don't understand why we had only two user sessions on that shared directory (in CROWD admin panel), while we have ~300 users concurrently working in JIRA/Confluence.
Your confusion is understandable; one login is a term which can mean one of 2 things:
1) The same username and password works across multiple applications, but you still have to sign on to each one separately (shared userbase). Crowd gets you this for free if you have JIRA/Confluence/other apps connected to it.
2) The same username and password works across multiple applications, and when once you have signed in to one application then you are automatically signed into all the applications (single sign on). Crowd supports this, but it requires a bit more configuration: https://confluence.atlassian.com/display/CROWD/Overview+of+SSO
If you are in situation 1 of the two listed above - that is, shared userbase but not sso (which I'm not sure of, but it sounds like that is the case) - then each application is connected to Crowd to check usernames and passwords but is creating and managing its own sessions, so Crowd doesn't know about those sessions.
If this still doesn't make sense, our support team can probably give you a better answer. They're smart guys and gals!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs