大网数据广告活动
服务器运维问答

ActiveDirectory LDAPS third-party certificate and internal names

· 52CE 我爱测

I have an AD RODC running on Server 2012 R2 Core in my perimeter network. I am using this for external/hosted applications that can do LDAPS based auth. My problem is that the FQDN of the server is an internal-only name (rodc-01.…

问题原文

原帖链接 · Joseph Alcorn · CC BY-SA 3.0

I have an AD RODC running on Server 2012 R2 Core in my perimeter network. I am using this for external/hosted applications that can do LDAPS based auth. My problem is that the FQDN of the server is an internal-only name (rodc-01.company.local). I have an A-record in external DNS and external DNS for a friendly name (auth.company.com). I have already verified that normal, non-SSL LDAP traffic over port 389 functions fine for both internal and external applications.

Ideally, I want to only use LDAPS, but according to Microsoft, the FQDN of the server needs to be either in the common name or the SAN of the certificate. Given that I need to use this with external applications, I need a trusted third-party certificate. I obtained one through GoDaddy for auth.company.com. The RODC refuses to recognize the certificate (CAPI2 logs provide a host-name mismatch error). Trusted third-party cert providers do not issue certs for .local domains. Is there a way around this? I can issue a cert from my internal CA infrastructure, but then the external applications refuse to connect because they don't trust the cert, and not all the applications enable me to provide them the cert to trust.

Does anyone have knowledge, or experience making this work? Microsoft has left us in a real bind by putting this requirement on LDAPS.

已采纳解答

原帖链接 · Joseph Alcorn · CC BY-SA 3.0

The power of posting... I finally found this article:

Basically, in order to do this, you have to have the cert in the NTDS services cert store. Problem is that on a SErver Core box, Microsoft provides exactly 0 offical utilities/tools to do this. You can not remotely add certs with private keys to the NTDS cert store, and you can't use the MMC snapin from the Core box, nor do certutil.exe or the built-in PowerShell cmdlets work with anything other than LocalMachine and Current user.

You have to export the registry key pertaining to your cert from the LocalMachine store and then import those settings into the registry into the NTDS cert store's registry location.

Following a reboot, LDAPS connections to auth.company.com were accepted with no problems whatsoever.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-02-14)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。