Grouper Developers Forum

[Tom Dopirak <>]

How difficult would it be to add a specific timezone on the permission limit 
syntax   , it seems that would make things easier to understand. You can 
alway default to the servers timezone. Perhaps I am overthinking this but 
international campuses will do that to you. 
On Jul 15, 2011, at 10:13 AM, Chris Hyzer wrote:

> Well, we haven't really heard a request for this.
> 
> Right now if you have a start or end date on a permission or membership, 
> then after midnight on the grouper server it will go live or dead.  This 
> wasn't really intended to be all that fine grained, though if someone needs 
> it, we could tweak.  Note that the start/end dates mean the membership or 
> permission is on or off, it wont be on for some timezones and off for 
> others.
> 
> For the times with permission limits (e.g. only allow from 9am-5pm on 
> weekdays), if the caller does not pass in the current time, it will use the 
> Grouper server time.  If the caller is in a different timezone, and passes 
> in the current time, then it will use that time.  So in that case the 
> permission could be allowed for some callers and disallowed for other 
> callers (depending on the clock of the caller).
> 
> Sound good?
> 
> Thanks,
> Chris
> 
> -----Original Message-----
> From: Tom Dopirak 
> [mailto:]
>  
> Sent: Friday, July 15, 2011 9:49 AM
> To: Tom Dopirak
> Cc: Chris Hyzer; Keith Hazelton; paccman; 
> 
> Subject: Re: [grouper-dev] Re: [paccman] built-in permissions limits... do 
> we need any more?
> 
> of course i meant grouper :)
> On Jul 15, 2011, at 9:37 AM, Tom Dopirak wrote:
> 
>> Hmmm. How do you expects dates to reflect internationalness? Is group 
>> timezone sensitive?
>> 
>> On Jul 7, 2011, at 1:14 PM, Chris Hyzer wrote:
>> 
>>> memberships and permissions have begin and end dates, so I dont think 
>>> someone would use permissions limits for that.  If there is a need we can 
>>> discuss :)
>>> 
>>> Thanks,
>>> Chris
>>> From: Keith Hazelton 
>>> []
>>> Sent: Thursday, July 07, 2011 12:50 PM
>>> To: Chris Hyzer
>>> Cc: paccman; 
>>> 
>>> Subject: Re: [paccman] built-in permissions limits... do we need any more?
>>> 
>>> For effective date (of memberships, etc), it would be good to have date 
>>> limits comparable to amount limits, e.g. "onOrAfter(2011-02-01) AND 
>>> notAfter(2011-10-31)"
>>> 
>>> It will be a big task to make this accessible for the average Grouper 
>>> (delegated) admin.  I can see that it will involve a lot of commentary on 
>>> each line of the code snippets, etc. plus a sense of what environment the 
>>> snippet assumes and what instances of what classes are in play.  A person 
>>> with a modest level of technical background should be able to go through 
>>> this document line by line, pose questions to Grouper-user and 
>>> occasionally Grouper-dev, and incorporate the verified answers into the 
>>> commentary.  
>>> 
>>> Very nice new capability, Chris, I especially like the flexibility and 
>>> extensibility of limit definition via expression languages.
>>> 
>>>     Regards,   --Keith
>>> 
>>> _______________________
>>> On Jul 1, 2011, at 09:10, Chris Hyzer wrote:
>>> 
>>>> Here are the built in limits I have implemented.  Its not the end of the 
>>>> world to miss one, we can add it later, and institutions can implement 
>>>> their own in the meantime, but if someone can think of another limit 
>>>> that would be nice to have, let me know, and if it is easy, I will add 
>>>> it (so far they have all been easy J ).
>>>> 
>>>> https://spaces.internet2.edu/display/Grouper/Permission+limit+builtin+implementations
>>>> 
>>>> Thanks,
>>>> Chris
>>>> 
>>>> From: Chris Hyzer 
>>>> Sent: Friday, June 17, 2011 10:39 AM
>>>> To: 'paccman'; 
>>>> ''
>>>> Subject: grouper permissions limits
>>>> 
>>>> FYI, this is where I see permissions limits going... let me know any 
>>>> feedback asap J
>>>> 
>>>> https://spaces.internet2.edu/display/Grouper/Grouper+permission+limits
>>>> 
>>>> btw, I will build the current state of 2.0 to the demo server at the end 
>>>> of the weekend.  J
>>>> 
>>>> Thanks,
>>>> Chris
>>> 
>>> 
>> 
>