Shibboleth Developers

[Tom Scavo <>]

On 4/19/05, Scott Cantor 
<>
 wrote:
> > I agree.  The profile tries to sneak in under the radar as a SAML
> > profile but really this is a Shibboleth profile and should be called
> > out as such.
> 
> No it isn't. It has *nothing* to do with Shibboleth. It's unfortunate that
> part of the attribute designator for these attributes contains a Shibboleth
> URN, but that doesn't make this a Shibboleth profile...

It's a Shibboleth profile in the sense that a non-Shibboleth
implementation would find the profile mostly unusable.  Looking ahead
to the SAML 2 attribute profile (in section 3), why would I want to
incorporate any of the deprecated elements in section 2?

> > Is eduPersonTargetedID (as an attribute)
> > totally obsolete with the arrival of SAML2?
> 
> I'm not prepared to preclude the transmission of that information using an
> attribute.

I wouldn't go that far either, but it lessens the urgency of having to
deal with eduPersonTargetedID right now.  In fact, until
eduPersonTargetedID is reconciled with the new SAML2 persistent name
identifier, it would seem best to do nothing.

> I'm more concerned about the 1.x profile at this point.

I'm not sure what all the hoopla is about.  If what you're trying to
do is pave the way for more widespread use of eduPersonTargetedID,
it's not clear why you want to do that right now.  You're just digging
yourself deeper into a hole.

Tom