Yvan Duhamel

icon indicating a website link https://fr.linkedin.com/in/yvand

icon company @Microsoft icon location Paris icon location Working mainly on SharePoint, Azure and Entra ID. Definitely the head in the clouds

Results 116 comments of Yvan Duhamel

Using Custom LDAPCP wsp and standard LDAPCP wsp

No, those are 2 different things. Let me clarify: - The claim provider needs to be associated with a trust to be able to create entities for that trust -...

Searching by Name on samAccountName

@weswilliams901 yes this is possible. To clarify: - In the green bold line: you must specify the LDAP attribute used by SharePoint to uniquely identify the user. It looks like...

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

@Paconaut to understand your scenario, can you please send the output of those commands: ```powershell Add-Type -AssemblyName "Yvand.LDAPCPSE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=80be731bc1a1a740" $config = [Yvand.LdapClaimsProvider.LDAPCPSE]::GetConfiguration() $config.Settings.ClaimTypes | ft LDAPAttribute, EntityType, ClaimType,...

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

Can you try to create the configuration using this command: ```powershell [Yvand.LdapClaimsProvider.LDAPCPSE]::CreateConfiguration() ```

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

Definitely looks like a bug, I will try to repro using the same claim types in the trust and come back to you, most likely next week. In the meantime,...

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

@Paconaut FYI, I was able to repro exactly the same error, I'll investigate and report the progress in this thread

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

I confirm this is a bug, fixed in https://github.com/Yvand/LDAPCP/pull/205

LDAPCPSE An item with LDAP newAttribute 'userPrincipalName' and LDAP class 'user' already exists for the object type 'User'

More info: It happens becaue you claim type `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/UPN` has upper-case letters `UPN`. A workaround to fix the issue on the current version, is to delete the trust and recreate...

LDAPCP Second Edition - MaxSearchResultsCount.

Hi @sgaukerud, indeed, I did not include this property in LDAPCP SE, because I did not think it was useful, and also because it overrides the max count that SharePoint...

LDAPCP Second Edition - MaxSearchResultsCount.

@sgaukerud I merged a PR today that re-adds the property `MaxSearchResultsCount`, it will be available in the next version. Its default value is -1 (which means it is ignored). To...