mpatrick210

Hey Yvand - I currently use LDAPCP v2017.10, and do not see a place to set the port. Do we need to update LDAPCP to a new version to see...

The option I have is "Secure" but don't have "SecureSocketsLayer"....but the adding ":636" behind the LDAP connection does not work...if the option "Secure" will force 636, I can give that...

@Yvand tried the "Encryption" type, and it fails with: Unable to connect to LDAP for following reason: The server is not operations. It may be expected if w3wp process of...

Hey @Yvand I was able to use our domain LDAP://domain.com:636 - but it would not allow us to add new users to sites via the People Picker on our production...

@Yvand Thank you for the further details...I will test these on my test environment and let you know what I find. Thanks!

hey @Yvand I will test this approach...my last tests seemed to work on my dev/test farms, but for the production farm, it seemed to break...it would allow "some" users, but...

Hey @Yvand just a quick follow up....I was able to get this to work, turns out it was an issue with cert chain...the reason it worked on lower tiers was...

In the ULS log it gives the error: Validation failed: found 0 entities instead of 1 for incmoing claim with value '[email protected]' and type "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"

Thank you for the update Yvand – looks like it may be fixed at this time? Thanks, Michael Patrick Lead Systems Administrator | T&I Solutions Delivery Deloitte Technology-US Deloitte Services...