<div>
The error occurs because - <br />
When generating a web certificate request from the TPAM appliance (see &quot;Generate web certificate request&quot; of TPAM_SysAdmin_Guide.pdf), the certificate generated by the Certificate Authority (.CER file) can only be imported back to the TPAM device where the .CSR file was generated.<br />
<br />
What to do - <br />
Re-issue the web certificate using the correct (or a new) certificate request generated from the appliance.<br />
<br />
For more information - <a href="https://support.software.dell.com/kb/145596" rel="ugc nofollow">https://support.software.dell.com/kb/145596</a>
</div>


<div>
Thanks Elizabeth,<br />
<br />
It's not for the appliance but Windows Server 2012 R2 Domain Controller and I have generated the CSR on the same machine and saved the certificate in the same folder where request file exists.
</div>


<div>
Try do it from the certificate GUI.<br />
<br />
Start &gt;&nbsp;Run &gt;&nbsp;certlm.msc &gt;&nbsp;Right click Personal &gt;&nbsp;All Tasks &gt;&nbsp;Import &gt;&nbsp;Find the cert you want (should be a .cer) &gt;&nbsp;import the certificate.<br />
<br />
Does anything different occur? Make sure you access the machine cert store.
</div>


<div>
Hi Learnctx,<br />
<br />
Yes, I am able to import that third party certificate from Certificate GUI while accessing the machine store.
</div>


<div>
OK, interesting you should be done then. AD should be serving up LDAPS on TCP 636.
</div>


<div>
Hi,<br />
<br />
Is there any online tool to test my LDAPS from outside of my organization?
</div>


<div>
From outside? Are you exposing your DC's to the Internet? :)<br />
<br />
The best tool to test LDAP and LDAPS is ldp.exe. Open it, the connect to LDAP and set the port as 636 and enable SSL. If you can successfully bind then LDAPS is working. If you are testing from an external location then you will also need to ensure the external party has your certificate chain trusted.
</div>


<div>
<div class="content wysiwyg-content">
I am following these guide to enable the LDAPs on one of my Windows Server 2012 R2:<br />
<br />
<a href="https://support.microsoft.com/en-us/kb/321051" rel="ugc">https://support.microsoft.com/en-us/kb/321051</a><br />
<a href="http://shabaztech.com/enabling-ldaps-certificate-3rd-party-ca/" rel="ugc">http://shabaztech.com/enabling-ldaps-certificate-3rd-party-ca/</a><br />
<br />
I already get the third party certificate with the extension .cer. Whenever, I try to run the command called certreq -accpet certfile.cer, it throws the following error:<br />
<br />
Certificate Request Processor: Cannot find object or property. 0x80092004 (-2146885628 CRYPT_E_NOT_FOUND)<br />
<br />
I tried to change the filename extension to .p7b and crt but still it gives the same error. <br />
<br />
Can anyone please help me in this regard?
</div>
</div>


I am following these guide to enable the LDAPs on one of my Windows Server 2012 R2:

https://support.microsoft.com/en-us/kb/321051
http://shabaztech.com/enabling-ldaps-certificate-3rd-party-ca/

I already get the third party certificate with the extension .cer. Whenever, I try to run the command called certreq -accpet certfile.cer, it throws the following error:

Certificate Request Processor: Cannot find object or property. 0x80092004 (-2146885628 CRYPT_E_NOT_FOUND)

I tried to change the filename extension to .p7b and crt but still it gives the same error. 

Can anyone please help me in this regard?

How to enable LDAP over SSL with a third-party certification authority?

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.