Skip to Content.

edugain-discuss - Re: [eduGAIN-discuss] [refeds] mari plan & next steps

edugain-discuss AT lists.geant.org

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

List archive


Re: [eduGAIN-discuss] [refeds] mari plan & next steps


Chronological Thread 
  • From: Leif Johansson <leifj AT sunet.se>
  • To: Niels van Dijk <niels.vandijk AT surfnet.nl>, REFEDS <refeds AT terena.org>, "edugain-discuss AT geant.net" <edugain-discuss AT geant.net>
  • Subject: Re: [eduGAIN-discuss] [refeds] mari plan & next steps
  • Date: Thu, 30 Oct 2014 15:10:34 +0100
  • List-archive: <https://mail.geant.net/mailman/private/edugain-discuss/>
  • List-id: eduGAIN discussion list <edugain-discuss.geant.net>

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

On 2014-10-30 09:25, Niels van Dijk wrote:
> On 29-10-14 16:06, Peter Schober wrote:
>> I'd be interested in more (any, really) concrete examples of
>> that kind of breakage, to substantiate the claim of the massive
>> scope of that problem. (I'm probaby just lacking that
>> experience, and imagination.)
>
> As an exmaple: I am currently building a service for eduGAIN that
> needs a persistent identifier for a user. My choices are: 1) SAML
> persistent NameID (preferred) 2) edupersontargetedid 3)
> eduersonperinciplename
>
> Neither of these is available in all federations connected to
> eduGAIN.
>
> Not a problem, I can programm around that. But I have no means of
> expressing that I need either of them in metadata. The only
> currently correct way of expressing this is to ask for a persistent
> NameID and have the two attributes as optional. This might actually
> lead to getting none.

Exactly.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlRSRtcACgkQ8Jx8FtbMZncKdgCglBJz8E4qBLFuiUd1UWmqxoNO
bKcAnjYrjxerB5IDFRjPxFLluVqrhCFX
=YX13
-----END PGP SIGNATURE-----






Archive powered by MHonArc 2.6.19.

Top of Page