COmanage Developers List

[Niels van Dijk <>]

Hi Ken, all,

Some comments and questions on your sheets:

@5: Just to be sure: not all tools listed are actually being offered as
services by SURFnet :)

@9,16,17: Just wondering (as we have been discussing this a lot
@SURFnet): Do you expect Comanage to behave statefull in regard to
attributes coming from the enterprise sources? Do you expect to
store/cache these attributes in Comanage? It seems that the STS will
require some form of statefullness? Also some provisioning en especially
deprovisioning might be a lot easier if the VO would be statefull.

@12: The VM bullet seems a bit out of place as this is an implementation
thing, while the other bullets are all on a functional level.
Additionally at the first bullet: Could a COManage instance serve as a
campus collab frontend? So put COmanage in a campus DMZ and use it to
integrate both remote and 'local' services.

regards,
Niels

On 04/05/2010 05:23 PM, Ken Klingenstein wrote:
> Folks,
>  Attached are a set of slides that try to work in some of my
> deliverables from last week's Comanage call. I'd appreciate comments on
> any of it, but in particular:
>     slides 7, 8, 9 - new - are they correct (apps are a different color
> to show that they can be somewhere else). is sts too visible? should
> ldappc be in there somewhere
>     slide 12 - do they answer the question of "what forms can COmanage
> take?"
>     slides 16-18 - are the flows illustrative? correct?
> 
>   After review, the slides are grist for anyone who might want to use
> them...
>         Ken

-- 
Niels van Dijk
Advanced Services

T: +31 302 305 337 / M: +31 651 347 657
SURFnet - PO Box 19035 - NL-3501 DA Utrecht - The Netherlands -

http://www.surfnet.nl
SURFnet - We make innovation work