Shibboleth Developers

[Ryan Muldoon <>]

My attribute URIs as defined in resolver.xml are correct.  Looking at my
target's shire.log, washington.edu and example.edu provided an Assertion
and an Authentication statement.  I'm only providing an Authentication
statement.  This is a result of something configured in resolver.xml,
right?  Or where else would this be defined/decided?

        --Ryan

On Wed, 2003-06-18 at 13:22, Scott Cantor wrote:
> > interesting. What might cause this?  As far as I can see, I'm 
> > not using incommon:pilot anywhere.  Any thoughts?
> 
> If your copy was old enough, your attribute URIs might be wrong. The target 
> would treat them as unknown attributes, see that they
> were strings, and just handle them as best it could, but the AAP would toss 
> them out as unacceptable, plus Apache wouldn't map them.
> 
> In general, you want to debug attribute issues from the target end. What is 
> it prepared to handle/accept?
> 
> In my case, it's handling:
> 
> urn:mace:dir:attribute-def:eduPersonPrincipalName
> urn:mace:dir:attribute-def:eduPersonScopedAffiliation
> urn:mace:dir:attribute-def:eduPersonEntitlement
> 
> If your resolver isn't sending those URIs, you'll get nothing.
> 
> -- Scott
> 

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--