Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] findByName

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] findByName

Chronological Thread 
  • From: Shilen Patel <>
  • To: Chris Hyzer <>
  • Cc: Tom Zeller <>, Grouper Dev <>
  • Subject: Re: [grouper-dev] findByName
  • Date: Thu, 19 Mar 2009 11:12:41 -0400

To remove a previous name should you have the same stem privilege you describe? :)

I was thinking ADMIN on the group would be good enough. Otherwise, the admin can just get around it by moving the group somewhere else and then back or by deleting the group and recreating it. :)


-- Shilen

On Mar 19, 2009, at 11:06 AM, Chris Hyzer wrote:

Yes, there are issues... :)

Your solutions looks good to me...

To remove a previous name should you have the same stem privilege you describe? :)

Might turn it into a mostly admin only thing, though it might not be a bad thing...


-----Original Message-----
From: Shilen Patel
Sent: Thursday, March 19, 2009 11:04 AM
To: Chris Hyzer
Cc: Tom Zeller; Grouper Dev
Subject: Re: [grouper-dev] findByName

Then do we actually check to see if the previous name being added was
actually a previous name for the group? If not, then what type of
privilege checking should we do? In addition to having ADMIN on the
group, perhaps the person should have CREATE access to the stem that
contained the previous name. And if that stem doesn't exist, we just
walk up the hierarchy until we find a stem that does exist and then
verify the CREATE privilege.

Would that work?


-- Shilen

On Mar 19, 2009, at 10:48 AM, Chris Hyzer wrote:

Cant we just have a group.addPreviousName(name) [which currently
replaces the current one] and group.deletePreviousName(name)? if
someone tries to use a previous name which is removed, then they
just add it back. If it is a question as to whether they know what
the name is, cant they look in the logs to see where the error is
occurring? And yes, I think we can assume people will use auditing,
and if they don't want to, we don't need to code around it.

These methods can be callable by GSH, and I can expose them via WS
and client fairly easily with the save group service (in the detail


-----Original Message-----
From: Shilen Patel
Sent: Thursday, March 19, 2009 7:56 AM
To: Tom Zeller
Cc: Grouper Dev
Subject: Re: [grouper-dev] findByName

Based on what I was hearing in previous discussions, this didn't
to be very important. Even though people might stop using the
previous name, having it remain in the system might not do any harm.
However, we can add the option to remove it if you think it would be
useful. But there may be more to consider.

So say if somebody removes a previous name then realizes that it's
still being used and so the user wants to add the previous name
How does that get handled?

One way might be to always populate the previous_name column but
have another column (previous_name_searchable) that determines if
group can actually be found using the previous name. The new
can be turned on and off by admins of the group. But if our future
method of doing multi-valued attributes won't be able to handle
then we might need a separate table for this data after all.

Another way might be to let admins of a group add back previous
based on audit data if that information is easy to query. But
everyone might not be using audit.

Perhaps we just give the user a warning saying that once you remove
the previous name, you cannot add it back (unless you go directly
the database of course).



-- Shilen

On Mar 18, 2009, at 4:14 PM, Tom Zeller wrote:

Are we also providing a method to remove previous name(s) ?


Archive powered by MHonArc 2.6.16.

Top of Page