InCommon eduGain and release policies

[Jeffrey Crawford]

Jeffrey E. Crawford
ITS Application Administrator (IdM)
831-459-4365
jeffreyc at ucsc.edu

Both pilots and IT professionals require training and currency before
charging into clouds!
---------------------------------------

On Fri, Jan 29, 2016 at 1:10 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > ​This may be an artifact of how I've got things configured currently,
> however if
> > I only rely on the absence of "registered-by-incommon" I'll pick up​
> > ​our local metadata as well, which has yet another default release
> policy.
>
> Can't you just attach a group name or entity attribute to that metadata
> and detect those specifically? I would leave "nothing" for the eduGain
> case...
>
​So something like eduGain = (!registerd-by-incommon) |
(​!local:metadata:group)

Since going to v3 I've been collecting them into a single metadata file,
but not all of them yet. Is using urn:mace:incommon really that big of a
problem? Seems more "exact" to me.


> You can always attach EntityAttribute extensions on the fly via metadata
> filter.
>
> > ​Does REFEDS R&S have more attributes than InCommon does? I'm sure it's
> > documented somewhere but I didn't find it quickly.
>
> Shouldn't.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160129/a6544276/attachment.html>