COmanage Developers List

[Benn Oshrin <>]

We need to flag this to a fix version for the roadmap. I'm going to 
throw this into 0.5 for now, mostly so we discuss it in Pasadena and 
push it to the correct release. It's probably more appropriate for 0.6 
or 0.7.

-Benn-

On 2/18/12 10:11 AM, Scott Koranda (JIRA) wrote:
> Scott Koranda created CO-253:
> --------------------------------
>
>               Summary: RFE CO/COU manager UI and functionality to expire 
> services
>                   Key: CO-253
>                   URL: https://bugs.internet2.edu/jira/browse/CO-253
>               Project: COmanage
>            Issue Type: New Feature
>            Components: Registry
>              Reporter: Scott Koranda
>              Assignee: Benn Oshrin
>              Priority: Major
>
>
> This is from an email from Stuart Anderson of LIGO:
>
> "More generally, perhaps a list of services should be presented to the group
> manager who is removing a member from their organization, where they can
> indicate a per service nominal expiry date and sponsor. Some future system 
> would
> then contact the sponsor at T-epsilon with a notification of pending 
> expiration
> if not action is taken and a pointer to a process to potentially extend access
> (which may require 3rd party authorization)."
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA 
> administrators: 
> https://bugs.internet2.edu/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira