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
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
Like I choose certain groups are JIRA groups and some are Confluence groups etc. That way the drop downs aren't so cluttered and people don't choose wacky groups when protecting spaces or pages. Oh and all of the system groups from my LDAP or AD don't find their way to the tools where they aren't relevant.
Wouldn't it be just a matter of not allowing everyone from a directory to authenticate (http://localhost:8095/crowd/console/secure/application/viewdirectories.action?ID=3), and then configure specific groups to authenticate (http://localhost:8095/crowd/console/secure/application/viewgroups.action?ID=3)?
I hope this helps!
No, not really. Yes, that controls who can authenticate and use the tool, but staying with Confluence, if I want to protect a page my available groups include hundreds of choices which have nothing to do with Confluence. This makes my ability to protect data extremely difficult. What I am asking about is a method where when I configure the application in Crowd, I choose which groups will sync with that application. If ten out of 500 are applicable then Confluence only has ten groups.