...
1. A course based at Brown includes students registered at Brown, as well as 14 students registered at a university in France. The brown-based instructor is able to compose an ldap-based group that includes the local students as well as the 14 french students (who access the brown-based services using their Federated credentials). The instructor is then able to grant this group write access to a space within Confluence. The local students use their brown credentials to access this space; the french students use their "local" credentials, and teh the Shibboleth software, to access this space.
2. A collaborative development effort at Cornell includes staff members from Indiana University as well. The JIRA project housing the development issues resides at Cornell and both universities leverage Shibboleth for institutional-specific SSO, giving them access to the same JIRA project. Integration with Shibboleth happens in one spot in Crowd, and JIRA hooks into Crowd. (hypothetical)
Managing Permissions
1. Allow a configuration where the server administrator can shut off the space administrators' ability to turn on anonymous edit. We don't allow that at our institution and don't want to let an instructor override our policy.
...
3. Along those lines, for semester-bound spaces, an easy way to programatically archive a list of spaces at the end of the term would be useful.
4. Several satellite instances of Confluence have been installed at Cornell and a current exercise is underway to migrate content from the satellite instances in departments, to the centrally scaled enterprise instance. Currently, migration between instances is somewhat manual although there seems to be standards patterns of data mapping that need to get addressed in the migration, such that a helper plugin could ease the burden of this work.