You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
It sounds like you are close to having it right.
Basically with crowd licensing, 1 Crowd License Seat is defined as a user who can authenticate to 1 or more applications.
http://www.atlassian.com/licensing/crowd#downloadlicenses-5
What you need to enusre is that only the groups you defined above for the variuos applications are the groups that are assigned to those applications and that under Directories in each Application, the allow all to authenticate is set to FALSE.
This means only the groups you specify for that application will allow those users to authenticate.
This will limit the number of users that crowd will calculate for its license count
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, keep them in OD, but assign the groups that you want to use for users of an application to that application under the Application Tab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.