Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Arbitrary attributes problem

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Arbitrary attributes problem


Chronological Thread 
  • From: "blair christensen." <>
  • To:
  • Subject: Re: [grouper-users] Arbitrary attributes problem
  • Date: Fri, 4 Aug 2006 10:01:55 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=oMu7XKk69m7vg9CzqhUZhWP4ff4iDaFNb+v3Uernwt3PhjjS3ORF6QTFa2nRWxJNxPbLtUVWNyDh+PqrzEUKnu45Ix6g0L3JVdzWi6njdSF9+0a/Z/xhuwdLHkail4ZZtn6mSn6jzOQ1FCyNUGL/ccanfm8D7SXK/3GNPrrgUsw=
On 8/2/06, GW Brown, Information Systems and Computing
<>
wrote:
The failure to save values is due to the way the UI uses the API. In
several places I use Group.getRemovableTypes - so I can exclude the base
type. This method requires you to be 'root':

if (PrivilegeResolver.getInstance().isRoot(this.getSession().getSubject()))

I can change my code, but is there any reason why this method should be
restricted, so long as Group.deleteType has appropriate checks?

This might have been due to a misunderstanding between the two of us
when you requested this method. I (apparently) thought the desired
behavior was to show what group types the acting subject could remove
from a group rather than all types that could in theory be removed.

Archive powered by MHonArc 2.6.16.

Top of Page