CN or DisplayName

[ghost]

Does anyone know how to properly import the claim of Displayname? I have ADFS Sending DIsplay-Name, but the peoplepicker keeps showing the UPN in the window. If i HOVER over the account, it is also showing the cn=(Users full name) which iisi what i want, but how do i have the peoplepicker show the Display Name there?

[Yvand]

hello, the people picker (so LDAPCP here) doesn't use what ADFS sends, it uses its own configuration to query LDAP server and display results.
If you want to show the display name in the people picker, go to central administration > security > LDAPCP global configuration: in section "Display of permissions created with identity claim", type property displayName in "Display another LDAP attribute"

[ghost]

Thanks, I’ll try that! From: Yvan Duhamel [mailto:notifications@github.com] Sent: Thursday, May 18, 2017 9:50 AM To: Yvand/LDAPCP <LDAPCP@noreply.github.com> Cc: aovecka <alex.ovecka@gmail.com>; Author <author@noreply.github.com> Subject: Re: [Yvand/LDAPCP] CN or DisplayName (#5) hello, the people picker (so LDAPCP here) doesn't use what ADFS sends, it uses its own configuration to query LDAP server and display results. If you want to show the display name in the people picker, go to central administration > security > LDAPCP global configuration: in section "Display of permissions created with identity claim", type property displayName in "Display another LDAP attribute" — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/Abbli6E3Lr_kTlfAjZiFWPkH58yhs39nks5r7ExvgaJpZM4NePy4> . <https://github.com/notifications/beacon/Abblizz3sFPWVNAT4wAAzNtISPSgSzkPks5r7ExvgaJpZM4NePy4.gif>

[Yvand]

Hello @aovecka, any news on that?

[ghost]

Sure! You have to make sure the ORDER of your mappings are correct and also the last powershell tag on your command uses -IdentifierClaim $upnclaimmap.InputClaimType Anotherwords, make sure the UPN is your main claim (Which is what is set in Active Directory for each user) and in the Claim Mapping config in the “Attirbute to display” I use the “cn” (common name) attribute which is their full display name. With that, it started working beautifully. From: Yvan Duhamel [mailto:notifications@github.com] Sent: Tuesday, July 04, 2017 9:16 AM To: Yvand/LDAPCP <LDAPCP@noreply.github.com> Cc: aovecka <alex.ovecka@gmail.com>; Mention <mention@noreply.github.com> Subject: Re: [Yvand/LDAPCP] CN or DisplayName (#5) Hello @aovecka <https://github.com/aovecka> , any news on that? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/Abbli8WxMMXiBazVyhG1ANPKlzUoBVT9ks5sKjsXgaJpZM4NePy4> . <https://github.com/notifications/beacon/Abbli2bOGE6kT-0knZ110HQPJazbUb54ks5sKjsXgaJpZM4NePy4.gif>

[Yvand]

Regarding the parameter "IdentifierClaim", I assume you talk about cmdlet New-SPTrustedIdentityTokenIssuer and indeed it's required SharePoint.
Regarding the order, I'm not sure I got your point
Anyway, I'm glad it works, and thank you for taking the time to reply

[ghost]

You're right, the order is not necessary. I didn't mean to call that out. But the identifier claim and then calling a different mapping.

…

On Thu, Jul 6, 2017 at 8:20 AM, Yvan Duhamel ***@***.***> wrote: Regarding the parameter "IdentifierClaim", I assume you talk about cmdlet New-SPTrustedIdentityTokenIssuer <https://technet.microsoft.com/en-us/library/ff607628.aspx>n and indeed it's required SharePoint. Regarding the order, I'm not sure I got your point Anyway, I'm glad it works, and thank you for taking the time to reply — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Abbli5_SUcgxSCq_uq-5-w2pJxeiS5wUks5sLNEfgaJpZM4NePy4> .