Re: Using cn (commonName) as NameID

[Robo Burned]

While I experienting hundreeds of issues trying to configure data connector and connection pool could anynody explain if it is really needed?
I found the following in docs:
Attribute Retrieval
LDAP attributes are returned as part of the authentication process and exposed in the LDAPResponseContext.
By default, attributes will be searched for using the same connection the user authenticated on. 
I've added cn to both
idp.authn.LDAP.returnAttributes= cn,passwordExpirationTime,loginGraceRemaining
and 
idp.attribute.resolver.LDAP.returnAttributes= cn,homephone,mail
Also uid attribute is available withoud configuring another LDAP connection.
So the question is Do one need to configure addional ldap connection if he needs attributes other than uid?
>Вторник, 24 ноября 2015, 15:29 UTC от "Doan, Tommy" <tdoan at smu.edu>:
>
>I believe Robo is missing the reference to a data connector in his attribute definition. Below is how we use CN in case it helps. 
>
>attribute-resolver.xml
><resolver:AttributeDefinition xsi:type="ad:Simple" id="commonName" sourceAttributeID="cn">
>  <resolver:Dependency ref="myLDAP" />
>  <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="urn:mace:dir:attribute-def:cn" />
>  <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="urn:oid:2.5.4.3" friendlyName="cn" />
></resolver:AttributeDefinition>
> 


Robo Burne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151125/272d29cc/attachment.html>