InCommon eduGain and release policies

Jeffrey Crawford jeffreyc at ucsc.edu
Fri Jan 29 15:17:44 EST 2016


Now that I've studied the preview metadata I'm starting to get the IdP
ready for eduGain. Hopefully without breaking existing InCommon stuff.

I wanted to go over a couple of points, I'll try and keep it short

1. There is a point in the getting ready guide that says use entity
attributes instead of the urn:mace:incommon "Group" name. However the
preview has that still included. For various reasons I'm trying to
distinguish between an InCommon identity, eduGain identity, and local
identity which has it's own group name. Is the following logic going to
work and be stable?:
(eduGain = group::urn:mace:incommon & (!attr::registerd-by-incommon))

2. There have been many discussions about what "identifier" is used in the
larger eduGain space. Since there is some local concern about releasing
eppn internationally, I'm planning on releasing persistant-id without eppn
to eduGain entities via nameIDFormatPrecedence and keep the current eppn +
transient-id combo in incommon. Do we risk large scale interoperability
issues with not releasing eppn for eduGain? I've seen many that have
transient as NameIDFormat listed first, and requested attributes, which we
will still honor via the consent page. But I'm worried there may be many
with transient requested and no AttributeRequests.

3. The reason we've been able to open the service up to wider SP's has been
the consent page. I have a pretty good handle on what can be "requested" on
the incommon side, but it looks like eduGain has requested attributes are
all over the map, does anyone have a list of "good to support" attributes
not covered by InCommon that should be considered in eduGain?

As a side note, we plan on treating all research and scholarship the same
way so we should be good there.

Thanks

Jeffrey
​ C.​
<jeffreyc at ucsc.edu>

Both pilots and IT professionals require training and currency before
charging into clouds!
---------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160129/930e3e69/attachment.html>


More information about the users mailing list