Issue with timeout on shibboleth.net

[Cantor, Scott]

We are still discussing, but just in the interest of transparency...what's likely to happen is us redeploying a Shibboleth SP in front of some of our systems, GitWeb being the primary one of public concern.

We should in one way or the other be able to get it into eduGAIN again like we used to do so it should be usable easily by a lot of the community, and we're not going to really authorize people in any meaningful way, as that's not a need.

I expect we will be willing to make some allowances for members that are not already members of a federation, but that is a relatively small set these days.

There are various reasons why this is a good step for us, both internally and externally, and one thing it will do is give us a testbed for SPv4, which we sorely need, and that will of course result in support for OpenID Connect eventually alongside SAML. It's not inconceivable that might be done fairly promiscuously given our requirements.

I don't have a timeline, but it likely won't be that long, the harder part is getting into eduGAIN again sustainably, not the SP deploy, and Seamless Access is of course a simple solution for discovery now that we didn't have in the old days.

-- Scott