将 ASP.NET ActiveDirectoryMembershipProvider 与林一起使用

发布于 2024-07-30 05:07:52 字数 1317 浏览 3 评论 0原文

我正在尝试设置一个 ActiveDirectoryMembershipProvider 来对抗森林，但我似乎无法让它工作。我们的一位 AD 管理员建议我参考全局目录，但似乎不受支持。任何人都知道您是否可以，如果可以，您如何配置 AD 成员资格提供程序来对抗森林？

以下是我尝试过的一些排列以及由此产生的错误。

<add name="ADConnectionString1"
    connectionString="LDAP://domain.org/DC=domain,DC=org:3268" />

“推荐已从服务器”

<add name="ADConnectionString2"
    connectionString="LDAP://domain.org/DC=domain,DC=org:" />

空引用异常。

<add name="ADConnectionString3"
    connectionString="LDAP://domain.org" />

空引用异常

<add name="ADConnectionString4"
    connectionString="LDAP://domain.org:3268" />

“GC 端口上的 LDAP 连接不支持 Active 目录。”

<add name="ADConnectionString5"
    connectionString="LDAP://domain.org:3268/DC=domain,DC=org:3268" />

“GC 端口上的 LDAP 连接不支持 Active 目录。”

<add name="ADConnectionString6"
    connectionString="LDAP://domain.org:3268/DC=domain,DC=org" />

“GC 端口上的 LDAP 连接不支持 Active 目录。”

原文

I'm trying to setup an ActiveDirectoryMembershipProvider to go against a Forest and I can't seem to get it working. One of our AD Admins suggested I refer to the global catalog but it seems that is not supported. Anyone know if you can and if so how do you configure the AD Membership Provider to go against a Forest?

Here are some of the permutations I've tried and the resultant errors.

<add name="ADConnectionString1"
    connectionString="LDAP://domain.org/DC=domain,DC=org:3268" />

"A referral was returned from the
server"

<add name="ADConnectionString2"
    connectionString="LDAP://domain.org/DC=domain,DC=org:" />

A null reference exception.

<add name="ADConnectionString3"
    connectionString="LDAP://domain.org" />

A null reference exception

<add name="ADConnectionString4"
    connectionString="LDAP://domain.org:3268" />

"LDAP connections on the GC port are
not supported against Active
Directory."

<add name="ADConnectionString5"
    connectionString="LDAP://domain.org:3268/DC=domain,DC=org:3268" />

"LDAP connections on the GC port are
not supported against Active
Directory."

<add name="ADConnectionString6"
    connectionString="LDAP://domain.org:3268/DC=domain,DC=org" />

"LDAP connections on the GC port are
not supported against Active
Directory."

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

偷得浮生 2024-08-06 05:07:52

我目前无权测试 ActiveDirectoryMembershipProvider，但全局目录搜索通常使用 GC:// 名称执行。例如，

    using (DirectoryEntry searchRoot = new DirectoryEntry("GC://DC=yourdomain,DC=com"))
    using (DirectorySearcher ds = new DirectorySearcher(searchRoot))
    {
        ds.Filter = "(sAMAccountName=userID1)";
        ds.SearchScope = SearchScope.Subtree;
        using (SearchResultCollection src = ds.FindAll())
        {
            foreach (SearchResult sr in src)
            {
                uxFred.Content = sr.Path;
            }
        }
    }

我在 ASP.NET 中工作时的建议始终是让您的搜索过滤器等使用 LDP 或只是一个普通的控制台/winform/wpf 应用程序。

I don't have access to test an ActiveDirectoryMembershipProvider at the moment but global catalog searches are usually performed using the GC:// moniker. E.g.

    using (DirectoryEntry searchRoot = new DirectoryEntry("GC://DC=yourdomain,DC=com"))
    using (DirectorySearcher ds = new DirectorySearcher(searchRoot))
    {
        ds.Filter = "(sAMAccountName=userID1)";
        ds.SearchScope = SearchScope.Subtree;
        using (SearchResultCollection src = ds.FindAll())
        {
            foreach (SearchResult sr in src)
            {
                uxFred.Content = sr.Path;
            }
        }
    }

My suggestion when working in ASP.NET is always to get your search filters, etc. working using LDP or just a plain console/winform/wpf app.

回复收藏 0 原文

~没有更多了~