<?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>PeteStilgoe.com &#187; SSO</title>
	<atom:link href="http://www.petestilgoe.com/category/sso/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.petestilgoe.com</link>
	<description>&#34;Be fearful when others are greedy, be greedy when others are fearful.”</description>
	<lastBuildDate>Mon, 30 Jan 2012 14:28:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>ADFS – Federated Web SSO with Forest Trust Scenario and its Limitations</title>
		<link>http://www.petestilgoe.com/2010/05/adfs-%e2%80%93-federated-web-sso-with-forest-trust-scenario-and-its-limitations/</link>
		<comments>http://www.petestilgoe.com/2010/05/adfs-%e2%80%93-federated-web-sso-with-forest-trust-scenario-and-its-limitations/#comments</comments>
		<pubDate>Thu, 27 May 2010 13:04:33 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[ADFS]]></category>
		<category><![CDATA[Sharepoint SSO]]></category>
		<category><![CDATA[SSO]]></category>
		<category><![CDATA[Windows / Active Directory]]></category>
		<category><![CDATA[active directory]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=583</guid>
		<description><![CDATA[

Hi, it&#8217;s Adam Conkle again. Today I’d like to talk about an ADFS case I had recently where the customer ran into some limitations with their Federated WebSSO with Forest Trust setup. They had their environment set up similar to what is described in Read Adams complete post here

]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2010/05/adfs-%e2%80%93-federated-web-sso-with-forest-trust-scenario-and-its-limitations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>K2 Blackpoint K2 Blackpearl does not support single sign on authentication</title>
		<link>http://www.petestilgoe.com/2010/03/k2-blackpoint-k2-blackpearl-doesn-not-support-single-sign-on-authentication/</link>
		<comments>http://www.petestilgoe.com/2010/03/k2-blackpoint-k2-blackpearl-doesn-not-support-single-sign-on-authentication/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 08:23:59 +0000</pubDate>
		<dc:creator>peter.stilgoe</dc:creator>
				<category><![CDATA[K2 Blackpearl]]></category>
		<category><![CDATA[K2 Blackpoint]]></category>
		<category><![CDATA[SSO]]></category>

		<guid isPermaLink="false">http://www.petestilgoe.com/?p=543</guid>
		<description><![CDATA[

FYI Neither K2 Blackpoint or K2 Blackpearl support SSO, they only support Windows authentication.  K2 Connect (SAP) makes use of SSO in some aspects.
If you are trying to use in an SSO environment you will see errors similar to:
Unable to cast object of type &#8216;System.Web.Security.SingleSignOn.SingleSignOnIdentity&#8217; to type &#8216;System.Security.Principal.WindowsIdentity&#8217;
Update: Apparently Blackpearl users can create a [...]]]></description>
		<wfw:commentRss>http://www.petestilgoe.com/2010/03/k2-blackpoint-k2-blackpearl-doesn-not-support-single-sign-on-authentication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

