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.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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