SPUserProfileSyncConnection SSL issue
See original GitHub issueHi,
I’m trying to configure an Active Directory Sync connection with SPUserProfileSyncConnection resource. I don’t have any problem if I’m not using SSL but if I set the UseSSL parameter to true, I’m getting the error:
The LDAP server is unavailable.
I’m trying with SharePoint 2016 on Windows Server 2016 with the SharePointDSC module version 2.1.0.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Can not create a user profile synchronization connection
I have a new SharePoint 2010 server farm that I'm trying to configure. Installation went fine. But I'm having trouble getting the user...
Read more >Synchronize user and group profiles in SharePoint Server ...
Learn how to synchronize user and group profile information by using the SharePoint Server 2013 profile synchronization method.
Read more >SSL Certificates, SharePoint, and User Profile ...
SharePoint is complex! Add in User Profiles and FIM Synchronization with SSL and SharePoint can become a administrator's worst nightmare.
Read more >[SOLVED] User Profile Synchronization Service Won't Start
I have watched ULS logs and it fails in the last step of trying to start services. I am waiting for the client...
Read more >User Profile Synchronization Service Stuck at "Starting"
Problem: SharePoint user profile synchronization service not starting! ... profile synchronization service account should have Farm Administrator access.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found the issue: When specifying UseSSL, you also have to specify that the port should be 636 instead of the default port 389. The code does not do this. Will update the resource, which will be included in my next Bugfix PR!
PR merged, closing issue