Attribute does not resolve and

Benjamin Cherian benjamin.cherian at villanova.edu
Wed Feb 4 11:10:07 EST 2015


I changed the definition so that the Attribute Definition ID is different
than the static attribute ID which is different than the SAML2 name. Still
seeing the same logs for the new ID where it is setting sourceAttributeID
to three different items. This is the new definition:

    <resolver:AttributeDefinition id="cqid" xsi:type="ad:Simple"
sourceAttributeID="cqUserAttribute">
        <resolver:Dependency ref="staticAttributes" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
name="cquser" encodeType="false" />
    </resolver:AttributeDefinition>


FWIW, this is IdP 3.0.

On 2/4/15, 10:46 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>>     <resolver:AttributeDefinition id="cquser" xsi:type="ad:Simple"
>sourceAttributeID="cquser">
>
>The semantics of this statement are, at best, wooly.  "Create an attribute
>called cquser based on a source attribute called cquser".  Which cquser do
>you want to use when?
>
>Of course it doesn¹t help that the encoded SAML2 name is 'cquser' either
>
>I'd suggest that you fix the naming either by renaming at the
>DataConnector
>or by using something other than cquser as the internal attribute
>(csuserAttribute?).  At that stage I suspect that at that stage the
>problem
>will go away.  
>
>-- 
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net



More information about the users mailing list