Subject: Grouper Users - Open Discussion List
- From: Chris Hyzer <>
- To: Keith Hazelton <>, "" <>
- Cc: "" <>
- Subject: RE: [grouper-users] group namespace practices
- Date: Tue, 19 Jun 2012 16:00:48 +0000
- Accept-language: en-US
Here is a naming wiki.
For the federated question, there is no official rule yet, but when we
discussed when designing fifer, we thought #2 was the only way to do that...
(backwards compatible with existing deployments)
That said, at Penn, our root stem is "penn", which every folder has as a
parent or ancestor...
On Behalf Of Keith Hazelton
Sent: Tuesday, June 19, 2012 11:53 AM
Subject: [grouper-users] group namespace practices
What guidelines are sites coming up with to set the left-hand portion of
their Grouper stem/folder hierarchy?
How are sites (if any are) preparing for a world of federated use of group
memberships? The options seem to include (among others):
1) Adopting a naming standard that guarantees global uniqueness of every
group (and folder) name
2) Using a flatter namespace for local groups and then, when the context
calls for it, globalizing them by adding a prefix (e.g.
urn:mace:foo.edu:groups:... or http://foo.edu/groups/....).
One could argue that any SAML use case might call for globalized group names
just in case they end up being used in non-local contexts
Inquiring minds..... --Keith
- [grouper-users] group namespace practices, Keith Hazelton, 06/19/2012
- RE: [grouper-users] group namespace practices, Chris Hyzer, 06/19/2012
Archive powered by MHonArc 2.6.16.