“域\用户名”的正式名称是什么？域的身份验证方法？
有谁知道基于“域\用户名”的登录的正式名称是什么？
我正在尝试对一个声称支持 LDAP 与 OpenLDAP、Sun One 等集成的应用程序进行故障排除。
当我查看日志并嗅探网络流量时，我可以看到在每个身份验证实例中都会传递“域\用户名” 。我不是 100% 确定，但我认为身份验证方法仅适用于 Active Directory？
预先感谢您能够提供的任何帮助；）
Does anyone know what the official name is for a "domain\username" based login?
I'm trying to troubleshoot an application which claims to have support for LDAP integration with OpenLDAP, Sun One etc.
When I reviewed logs , and sniffed the network traffic I could see that in every instance of authentication a "domain\username" is passed. I'm not 100% sure but I think that method for authentication is only for Active Directory?
Thanks in advance for any help you may be able to provide ;)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
“Windows 身份验证”
"Windows authentication"
Active Directory，现在是更大的 Active Directory 域服务
Active Directory, now part of the greater Active Directory Domain Services
这可能有点令人困惑，因为活动目录能够使用多种身份验证机制进行身份验证。使用哪种功能取决于域策略和客户端功能。因此 AD 可以使用 Kerberos、NTLM 或 LDAP 绑定进行身份验证。通常 Kerberos 是首选。
因此，也许您的应用程序具有多协议功能，并且由于它在 AD 域中运行，因此默认为 Kerberos，但如果它在仅 LDAP 的环境中运行，则默认为 LDAP 绑定。
This can be a bit confusing because active directory is capable of authenticating with multiple authentication mechanisms. Which capability is used is based on domain policy and client capabilities. So AD could be authenticating with Kerberos, or NTLM or LDAP bind. Usually Kerberos is preferred.
So maybe your application in question is multi-protocol capable and because it is operating in an AD domain it is defaulting to Kerberos, but if it were operating in an LDAP only environment it would default to LDAP bind.
我相信这些“域\用户名”登录是 NTLM 登录。
I believe these "domain\username" logins are NTLM logins.
域\用户名通常由 AD 管理，并且通常基于 NTLM 身份验证。如果您的应用程序声称它可以与 OpenLDAP 集成，那么这并不意味着它正在使用基于 LDAP 的身份验证。这可能意味着它可以与 OpenLDAP 同步其用户和更改基于系统，它可能有一些用于此目的的 API。
Domain\username is usually managed by AD and usually based on NTLM authentication.If your application claims it can integrate with OpenLDAP then it doesn't mean it is using LDAP based authentication.It could mean it can synchronize its users and changes with an OpenLDAP based system and it might be having some APIs for this.