<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Matthieu &#124; Blog &#187; active directory</title>
	<atom:link href="http://matthieu.yiptong.ca/tag/active-directory/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthieu.yiptong.ca</link>
	<description>A bit of photos, a bit of tech. Add some thoughts, and here&#039;s what you get.</description>
	<lastBuildDate>Fri, 03 Feb 2012 16:56:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Allowing LDAP to read users from child domain in a forest</title>
		<link>http://matthieu.yiptong.ca/2009/07/06/allowing-ldap-to-read-users-from-child-domain-in-a-forest/</link>
		<comments>http://matthieu.yiptong.ca/2009/07/06/allowing-ldap-to-read-users-from-child-domain-in-a-forest/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 17:36:06 +0000</pubDate>
		<dc:creator>Matthieu</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[ad]]></category>
		<category><![CDATA[child domain]]></category>
		<category><![CDATA[LDAP]]></category>
		<category><![CDATA[openfire]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[read]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://matthieu.yiptong.ca/?p=4</guid>
		<description><![CDATA[Quick note: using LDAP&#8217;s default port 389 with a Base DN of the parent Active Directory domain only shows objects from the parent domain. Changing the port to 3268 but keeping the same Base DN allows LDAP access to users from the child AD domain. So, finally got the Openfire Jabber server to see all [...]]]></description>
			<content:encoded><![CDATA[<p>Quick note:<br />
using LDAP&#8217;s default port 389 with a Base DN of the parent Active Directory domain only shows objects from the parent domain. Changing the port to 3268 but keeping the same Base DN allows LDAP access to users from the child AD domain.</p>
<p>So, finally got the Openfire Jabber server to see all users from both domains.</p>
<p>Found via: <a href="http://www.igniterealtime.org/community/message/155746">http://www.igniterealtime.org/community/message/155746</a></p>
<p>For further reading: <a href="http://technet.microsoft.com/en-ca/library/cc978012.aspx">http://technet.microsoft.com/en-ca/library/cc978012.aspx</a></p>
<p>Kind of a lame first post, but hey, gotta start somewhere!</p>]]></content:encoded>
			<wfw:commentRss>http://matthieu.yiptong.ca/2009/07/06/allowing-ldap-to-read-users-from-child-domain-in-a-forest/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

