edugain-discuss AT lists.geant.org
Subject: An open discussion list for topics related to the eduGAIN interfederation service.
List archive
- From: Niels van Dijk <niels.vandijk AT surfnet.nl>
- To: edugain-discuss AT geant.net
- Subject: [eduGAIN-discuss] eduGAIN metadata requirements in regard to discovery
- Date: Tue, 23 Dec 2014 13:49:28 +0100
- List-archive: <http://mail.geant.net/pipermail/edugain-discuss/>
- List-id: "An open discussion list for topics related to the eduGAIN interfederation service." <edugain-discuss.geant.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
thanks!
Niels
- --
Please note:
On January 1st, 2015 SURFnet will move to a new office.
Visiting address: Kantoren Hoog Overborch (Hoog Catharijne)
Moreelsepark 48, 3511 EP Utrecht
Postal address: PO Box 19035, 3501 DA Utrecht
Telephone: +31 88-7873000
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJUmWTXAAoJECCFeCvee7L1R+AP/ie2ZQoqdSP6IBK0E4rIOsr/
DDS6KPdodmRQFPlF7IlsjzI5NLC+ECBd29Dixcut9n8LLfa0h7dZ7BzSUB22hcpA
zxHuUEEM8zgjHwopat6FD9DHsQcC4h+Tk+BCgRtK3hM9luPqPvYqvUgGVMAL6BPT
Rx2EhkVbtmuI2m1ouRHbB3AnQgw0m7CvV5k7vkW68xpkvycTVd7qxl4SXGekUnfm
zZ4izfNEcl6/1NfA+6rU2L0hsERR/5pP+LJChK8HCDdPIv4TNCql2QX0+YoqrWmJ
MWHQGLNbyWRN02mEYNXL+oBHbnf37eFWl3JwOqhnVar1mJzyottVRWrqj08V537K
gmuvb6w4K6O9rzkBQfjs8q2Fq2eseQJuLMf1Cm9/3TiukUpccWlQAsPPHg6Rv6uL
S+gIshO1hkUQEqNONnSTBe+8TuZDXsbUMf+6rfBnqLsvYdigQx5nHEd3MtdHCIq5
kAXeAsQb/zIVKsoVO9evILTY4gzi0vRkux5Wz7d3v3TsqL0u2H75JAWOdPaYXm0M
1Vc5VC+vftSF3zikecw2DStDbmazbp3OuYelcdH47O3gnYif1/kdbCvQqhFJAfTq
AQIaVDr9uJ7BQ18bZEij8khOn0diLk4DFrUIBBtd4zND/M+R7LDs9zUK6n0occsV
gQyChH2Qs15QIXooEwq4
=ILle
-----END PGP SIGNATURE-----
- [eduGAIN-discuss] eduGAIN metadata requirements in regard to discovery, Niels van Dijk, 12/23/2014
- Re: [eduGAIN-discuss] eduGAIN metadata requirements in regard to discovery, Leif Johansson, 23-Dec-2014
Archive powered by MHonArc 2.6.19.