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

[Leif Johansson <leifj AT sunet.se>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/23/2014 01:49 PM, Niels van Dijk wrote:
> Hi all,
> 
> Reading through the eduGAIN metdata requirements (Which I think
> live here: 
> http://services.geant.net/edugain/Resources/Documents/eduGAIN_metadata_profile_v3.doc)
>
>  I get the impression we have done our best to make IdP discovery
> as hard as possible:
> 
> - We do not require a display name for an IdP at all, neither in
> the native language nor in English. - We do not require a logo;
> actually the logo is not even mentioned in the document as a
> could/should. As such there is no recommendation on size and on the
> way to present it (url vs embedded).
> 
> Basically, when literally interpreting the mandatory parts of the 
> spec, the only reasonable thing for an SP to do is to fall back to 
> presenting the entityID. Typically not something a user will 
> understand intuitively...
> 
> I understand that we may want to keep the level of entry as low as 
> possible but what users get served by an IdP they cannot find in a 
> discovery? Or am I missing something here?

I actually don't think the edugain documents matter that much (in this
respect) when it comes to actual deployment.

Instead I suspect those of us who implement discovery services will do
a reasonable job to use whatever information is found in metadata to
present something useful to the user.

As mdui-aware discovery services become more common there will be a
natural pressure to provide more information in metadata which will
resolve the issue eventually.

        Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSZaMgACgkQ8Jx8FtbMZnf5BACfdW5nnQMVd6DsbJQh1PMCmCG+
2r0AnAp+v6hngedqFh8WrVAtVzJ7kQ0W
=2dIS
-----END PGP SIGNATURE-----