Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] namespace transaction issue, and group name aliases

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] namespace transaction issue, and group name aliases


Chronological Thread 
  • From: "GW Brown, Information Systems and Computing" <>
  • To: Chris Hyzer <>, Grouper Dev <>
  • Subject: Re: [grouper-dev] namespace transaction issue, and group name aliases
  • Date: Thu, 05 Feb 2009 08:12:39 +0000

My use cases for stem aliases are similar:
1) Supporting multiple hierarchies so that stems/groups can be found straightforwardly by individuals with different roles and, therefore, different expectations - this is similar to Bert's use case where department members have different needs to a sys admin.

2) Sometimes a strict hierarchy just doesn't work - we have course modules which may be taken by students on different courses from different departments. From the Staff or Student point of view groups associated with the module belong under both department/course trees. This is more a navigation issue than wanting stem aliases to be interchangeable in config files.

Given that course modules etc will often be represented by more than one group it is often more appropriate to create a stem alias than lots of group aliases. I understand there are more implications for stem aliases but it has been on my wish list from the very first call Bristol had with Tom and blair when we got involved with Grouper - more consistency Tom :)

Gary



--On 04 February 2009 17:12 -0500 Chris Hyzer
<>
wrote:



Btw, might there be grouper configuration that breaks due to someone
renaming something?



e.g. the ldap provisioning example where the provisioned groups are from
a stem in the ldappc.xml file, if someone moves that, then those might
not get provisioned… if there is an alias, then it might, if it is sql
driven, then it might not.



Also, I made a group name alias wiki a while back:



https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+aliases



I just added this:



Here is a potential table design:

table: grouper_group_alias

col: group_id

col: group_alias_name

col: last_edited

col: expire_timestamp

I guess we need another one for stem name aliases, or we can add that in
to this one, with stem_id col... will we have aliases on other things
too? attributes, etc? or just group names, and maybe stem names? Is
there a use case for stem aliases? I cant think of one, except if a
system is checking a stem privilege for some sort of access… hmmm





Chris









----------------------
GW Brown, Information Systems and Computing




Archive powered by MHonArc 2.6.16.

Top of Page