An open discussion list for topics related to the eduGAIN interfederation service.

[Nick Roy <nroy AT internet2.edu>]

There are defensive measures that should be standard operating procedure for 
any infrastructure upgrade, and testing and notification to those downstream 
is one of those standard things. I don't recall ever being notified via the 
eSG or anywhere else that the introduction of the new version of the eduGAIN 
SAML profile would introduce differences like the one that started this 
thread.

Nick

On 20 Nov 2019, at 9:24, Peter Schober wrote:

> * Etienne Dysli Metref <etienne.dysli-metref AT switch.ch> [2019-11-20 17:17]:
>> edugain-sg seems to be a closed list though (no public archive).
>
> "sg" stands for "steering group", so yes, it's a closed list.
>
> The expectation so far (well, at least my own) has been that the 2
> people per federation who are official delegates -- see
> https://technical.edugain.org//governance -- would share / pass
> onrelevant information within each federation.
>
> In this case I guess noone (in charge) was aware that an update might
> cause this (that bug having been reported in 2011 notwithstanding),
> otherwise this would have been communicated, of course.
>
> Shit happens, and usually when you're not expecting it to happen.
>
> This is a bit like people complaining why there was no log event about
> some software crashing -- well, the software was crashing, it didn't
> have time to write that it was about to crash to the log. ;)
>
> Cheers,
> -peter

Attachment: signature.asc
Description: OpenPGP digital signature