Shibboleth Developers

[Michael Gettes <>]

Just to you... Any chance for discussing n-tier solutions such as kerberos would be heat... :-)

/mrg

-----Original Message-----
From: Steven Carmody []
Received: Wednesday, 13 Apr 2011, 7:29
To: []
Subject: Re: [Shib-Dev] Proposed Shib WG topics

On 4/7/11 1:18 PM, Tom Scavo wrote:
> On Thu, Apr 7, 2011 at 10:54 AM, Chad La Joie<>  wrote:
>>
>> - Univ of Florida's Shib deployment description including how they mange
>> their 300+ SPs
>
> +1
>
>> - New ways in which the Shib software is consuming and using metadata
>> for filtering, crypto algorithm selection, and UI presentation
>
> +1
>

Tom -- thanks for the feedback. But, as we've seen, the overall response
has been very low. I think the Shib WG session has evolved to become a
meeting of IC Federation members. Consequently, attendees are more
focused on the "now" - on things they can do and things that will affect
them between now and the Fall I2 meeting. For most, IDP v3 is very far
away, except for big functionality issues. I think this request for
votes could have been posted to a different list, one with more deployers.

We have to settle an agenda soon, though, so we can get it posted to the
meeting website. Given the lack of response, I think we should pick
topics that will be relevant in the short term . And there may be some
topics that could be covered in 5-10 minutes.

Here's my suggestions

- Univ of Wisconsin's IdP 2.x extension for implementing basic SP access
control at the IdP. (5 min; just yesterday someone posted a problem to
shib-users that could be addressed with this functionality)

- Univ of Florida's Shib deployment description including how they mange
their 300+ SPs (10 min)

-- stateless clustering (5-10 min; Scott's approach; again, lots of
questions)

- New ways in which the Shib software is consuming and using metadata
for filtering, crypto algorithm selection, and UI presentation (5-10 min)

- UI changes to improve the whole login process user experience (defer;
some of this is being covered in the InCommon sessions)

We should get this settled today.