# LDAPS and Self SIgned Certificates **URL:** \ **Category:** Ignition\ **Created:** [February 3, 2021, 7:22pm UTC](https://forum.inductiveautomation.com/t/ldaps-and-self-signed-certificates/42978 "2021-02-03T19:22:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [February 3, 2021, 7:56pm UTC](https://forum.inductiveautomation.com/t/ldaps-and-self-signed-certificates/42978/2 "2021-02-03T19:56:50Z")
You'll need to install your AD's self signed cert as a trusted cert on the gateway; see this thread for more details: > [@SSL/TLS How-to for Active Directory LDAPS User source](http://forum.inductiveautomation.com/t/solved-active-directory-ldaps-for-user-source-ldaps-ssl-how-to/28235/23): > > As both @Kevin.Herron and @ryanjmclaughlin have mentioned, just by dropping the certificate into the data\certificates\supplemental folder, and restarting the Gateway did the trick for me. If that didn’t work for you, maybe you can check the following settings: Primary Domain Controller Port: I have successfully used both 636 and 3269. Use SSL: Checked. Security Protocol: SSL (although Auto worked on a recent 8.0.14 installation). And to check if the certificate was imported correctly, … --- _[View the full topic](https://forum.inductiveautomation.com/t/ldaps-and-self-signed-certificates/42978)._