Grouper Developers Forum

["caleb racey" <>]

That would be a good idea, always worth recording why certain routes where 
not taken.
 
JISC rules say the project website has to have a lifecycle of atleast 5 years 
so it's not going to go away (we are at end of year 1) . 
 
If you want to take the text and stick it in the internet2 documentation we 
are more than happy. the project uses a creative commons Attribution-Share 
Alike 3.0 License. <http://creativecommons.org/licenses/by-sa/3.0/>    but if 
that is incompatible with internet2 we are more than happy to relicence it 
under whatever works. 
 
cheers
 
Cal

________________________________

From: Tom Barton 
[mailto:]
Sent: Thu 5/15/2008 4:56 PM
To: caleb racey
Cc: Grouper Dev
Subject: Re: [grouper-dev] Grouper design call, Wednesday, 14 May 2008, 
1200EDT (1600Z)



Nice work. Do you think it would be valuable and appropriate if this was
linked from some suitable part of the grouper doc?

Tom

caleb racey wrote:
>>    . protecting grouper-ws with apache + mod_proxy_ajp
>
>
> We have just published sanjay's report on his investigations of various
> techniques for authenticating webservices  linked to from
> http://gfivo.ncl.ac.uk/resources.php
>
>
> The 10 second summary is: There are theoretical techniques for deploying
> a webservice once and using different auth routes (multiple policy, or
> multiple port), however the reality is that they are poorly supported.
> Deploying the same webservice app twice and deploying different auth on
> top of each is much easier and works.
>
>
> Cheers
>
> Cal
>
> --------------------
> Caleb Racey
> Team Leader
> Middleware Team
> ISS
> Newcastle University
> --------------------