Attribute not encoded because no SAML2AttributeEncoder was attached to it

[Saurabh Tyagi]

Dear Peter,

Thanks for response. 
Actully I am very new to Shibboleth and some time unable to understand what
u wanna say. 
So ask same question when unable to understand .

Thanks again, that you are helping every time I ask question.
You are a greate help to the community.


Thanks and Regards
Saurabh Tyagi


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On
Behalf Of Peter Schober
Sent: Friday, June 28, 2013 7:36 PM
To: users at shibboleth.net
Subject: Re: Attribute not encoded because no SAML2AttributeEncoder was
attached to it

* Saurabh Tyagi <saurabh.tyagi at thepsi.com> [2013-06-28 16:00]:
> Solved by Adding in attribute-resolver.xml
> 
> <resolver:AttributeEncoder xsi:type="SAML2String"
> xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
> name="mail"></resolver:AttributeEncoder>

Why not "solve" it by restoring the default configuration, like in the
URL I sent before (just copy & paste from there):

    <resolver:AttributeDefinition xsi:type="ad:Simple" id="email"
sourceAttributeID="mail">
        <resolver:Dependency ref="myLDAP" />
        <resolver:AttributeEncoder xsi:type="enc:SAML1String"
name="urn:mace:dir:attribute-def:mail" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="mail" />
    </resolver:AttributeDefinition>

Then you'll at least have the proper name and nameformat.
Same for "cn".
-peter
--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net