Title: Unknown CA when using plugin
Last modified: January 5, 2017

---

# Unknown CA when using plugin

 *  [battlezilla](https://wordpress.org/support/users/battlezilla/)
 * (@battlezilla)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/unknown-ca-when-using-plugin/)
 * Hello,
 * I am having a problem with the plugin using LDAPS. It won’t authenticate. After
   doing a packet trace we are seeing an Unknown CA ERROR.
 * Any Ideas?
 * Bitnami WordPress appliance
    Wordpress 4.7 NADI 2.0.11 LDAP = Server 2012 R2 
   secured with internal and external CA.
 * Thanks.
 * Lamar

Viewing 1 replies (of 1 total)

 *  [medan123](https://wordpress.org/support/users/medan123/)
 * (@medan123)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/unknown-ca-when-using-plugin/#post-8625108)
 * Hello Lamar,
    If you would like us to take a look at your specific problem, please
   buy a support license at [https://active-directory-wp.com/](https://active-directory-wp.com/).
 * Have a nice day
 * medan123

Viewing 1 replies (of 1 total)

The topic ‘Unknown CA when using plugin’ is closed to new replies.

 * ![](https://ps.w.org/next-active-directory-integration/assets/icon-256x256.png?
   rev=2517660)
 * [Next Active Directory Integration](https://wordpress.org/plugins/next-active-directory-integration/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/next-active-directory-integration/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/next-active-directory-integration/)
 * [Active Topics](https://wordpress.org/support/plugin/next-active-directory-integration/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/next-active-directory-integration/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/next-active-directory-integration/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [medan123](https://wordpress.org/support/users/medan123/)
 * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/unknown-ca-when-using-plugin/#post-8625108)
 * Status: not resolved