Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Jane,

 

Im not going to copy your email here, but basically you asked me whether applications should consume memberships using the group uuid or the group system name (which includes the path).

 

I think everyone who uses grouper uses the group system name (which includes path).  If anyone consumes UUID or recommends that please correct me.

 

Here are my reasons:

 

1.       There is a display name and a system name.  To change how the group displays in the UI, change the display name.  This doesn’t affect applications

2.       If you change the system name, which you shouldn’t in general, there is an alternate name which can also refer to the group.  Sort of like a symbolic link.  Even with this feature, system names generally shouldn’t be changed

3.       Yes, educate delegated users to not change the system name

4.       There is value in applications integrating with a human readable name so they know what they are using.  Otherwise I would think the wrong UUID could be used by accident.

5.       When setting up folders, try to do so in a way where wont change system names in the future J   (e.g. for org charts, don’t put hierarchy in folder structure)

 

Of course some apps could use uuid if they want.  But yes, its good to have institutional standards.  Is this topic covered in the grouper deployment guide?

 

Ok?  J

 

Yes we can discuss on the phone sometime if you like.

 

Thanks

Chris