<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Integrated Authentication and Exchange 2007</title>
	<atom:link href="http://www.shudnow.net/2007/09/27/integrated-authentication-and-exchange-2007-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shudnow.net/2007/09/27/integrated-authentication-and-exchange-2007-problem/</link>
	<description>Just another IT guy!</description>
	<lastBuildDate>Wed, 08 Sep 2010 21:02:40 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: JSmith</title>
		<link>http://www.shudnow.net/2007/09/27/integrated-authentication-and-exchange-2007-problem/comment-page-1/#comment-7866</link>
		<dc:creator>JSmith</dc:creator>
		<pubDate>Thu, 20 Aug 2009 16:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/2007/09/27/integrated-authentication-and-exchange-2007-problem/#comment-7866</guid>
		<description>GREAT Post.  You spelled out the &#039;limitations&#039; precisely (as I&#039;ve been encountering anyway), so that I didn&#039;t get lost between the lines of the M$ articles that only spell out what is supported.

We user Windows/Integrated Auth for our entire Intranet here, and there are several applications across several webservers that provide my users with alot of stuff, in one place.  It&#039;s silly to have them log into their PC&#039;s and then into the website, so Integrated/Windows Auth solved this.

I am mid-Migration to Exch2007 but now I have to wait until all mailboxes are moved to Exch2007 MB Role, for the Integrated Auth to work for them for their email; if they use it via OWA.

I think this is an oversight on M$ part.  Lots with Exch2007 are wonderful, especially the new OWA; but the coexistence piece has alot of missing pieces I think.

One work around I&#039;m am working towards is using ISA as the Publishing Front End.  Currently it has FBA for the outside, and therefore proxies Basic Auth into the CAS, and thus OWA works great for both versions through the CAS.  I think if I enable an internal Web-Listener on ISA with Integrated Auth, ISA will proxy Integrated Auth to the CAS, and I will be no further ahead, but I think I might try.</description>
		<content:encoded><![CDATA[<p>GREAT Post.  You spelled out the &#8216;limitations&#8217; precisely (as I&#8217;ve been encountering anyway), so that I didn&#8217;t get lost between the lines of the M$ articles that only spell out what is supported.</p>
<p>We user Windows/Integrated Auth for our entire Intranet here, and there are several applications across several webservers that provide my users with alot of stuff, in one place.  It&#8217;s silly to have them log into their PC&#8217;s and then into the website, so Integrated/Windows Auth solved this.</p>
<p>I am mid-Migration to Exch2007 but now I have to wait until all mailboxes are moved to Exch2007 MB Role, for the Integrated Auth to work for them for their email; if they use it via OWA.</p>
<p>I think this is an oversight on M$ part.  Lots with Exch2007 are wonderful, especially the new OWA; but the coexistence piece has alot of missing pieces I think.</p>
<p>One work around I&#8217;m am working towards is using ISA as the Publishing Front End.  Currently it has FBA for the outside, and therefore proxies Basic Auth into the CAS, and thus OWA works great for both versions through the CAS.  I think if I enable an internal Web-Listener on ISA with Integrated Auth, ISA will proxy Integrated Auth to the CAS, and I will be no further ahead, but I think I might try.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
