<?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: Leveraging CAS with Luminis</title>
	<atom:link href="http://nosheep.net/story/leveraging-cas-in-luminis/feed/" rel="self" type="application/rss+xml" />
	<link>http://nosheep.net/story/leveraging-cas-in-luminis/</link>
	<description>Comic book guy, tech geek, and father of two...</description>
	<lastBuildDate>Sat, 13 Mar 2010 12:39:02 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: No Sheep &#187; Shibboleth For AuthZ</title>
		<link>http://nosheep.net/story/leveraging-cas-in-luminis/comment-page-1/#comment-4137</link>
		<dc:creator>No Sheep &#187; Shibboleth For AuthZ</dc:creator>
		<pubDate>Tue, 27 Jun 2006 13:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-cas-in-luminis/#comment-4137</guid>
		<description>[...] Until this point I had only though of Shibb as a solution for inter-organizational web-based single-sign on (Federated SSO or WebISO or WebSSO). I knew I could use Shibboleth internally to serve as my WebSSO, but we already have a hugely successful implementation of CAS in our environment. Additionally I haven&#8217;t been able to point at a killer application of the federated WebSSO ability. I knew this driver would be coming, but without immediate demand I was luke warm on Shibboleth. [...]</description>
		<content:encoded><![CDATA[<p>[...] Until this point I had only though of Shibb as a solution for inter-organizational web-based single-sign on (Federated SSO or WebISO or WebSSO). I knew I could use Shibboleth internally to serve as my WebSSO, but we already have a hugely successful implementation of CAS in our environment. Additionally I haven&#8217;t been able to point at a killer application of the federated WebSSO ability. I knew this driver would be coming, but without immediate demand I was luke warm on Shibboleth. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Identity Future &#187; Blog Archive &#187; Leveraging CAS with Luminis</title>
		<link>http://nosheep.net/story/leveraging-cas-in-luminis/comment-page-1/#comment-1788</link>
		<dc:creator>Identity Future &#187; Blog Archive &#187; Leveraging CAS with Luminis</dc:creator>
		<pubDate>Fri, 31 Mar 2006 14:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-cas-in-luminis/#comment-1788</guid>
		<description>[...] From NoSheep.net&#8217;s article:  In SunGard Higher Education&#8217;s Luminis product one of the many add-on packages you can install is CAS support. CAS is an acronym for Central Authentication Service. This WebISO solution is one of the most common in higher education. CAS was created originally by Yale, but ongoing support has been taken over by JA-SIG. When the CAS package is installed in Luminis, it makes Luminis act as a CAS authentication provider. Coupled with this built-in Luminis support, we use a CAS library called phpCAS that adds to the simplicity of deploying this within our environment. [...]</description>
		<content:encoded><![CDATA[<p>[...] From NoSheep.net&#8217;s article:  In SunGard Higher Education&#8217;s Luminis product one of the many add-on packages you can install is CAS support. CAS is an acronym for Central Authentication Service. This WebISO solution is one of the most common in higher education. CAS was created originally by Yale, but ongoing support has been taken over by JA-SIG. When the CAS package is installed in Luminis, it makes Luminis act as a CAS authentication provider. Coupled with this built-in Luminis support, we use a CAS library called phpCAS that adds to the simplicity of deploying this within our environment. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zbtirrell</title>
		<link>http://nosheep.net/story/leveraging-cas-in-luminis/comment-page-1/#comment-1743</link>
		<dc:creator>zbtirrell</dc:creator>
		<pubDate>Wed, 29 Mar 2006 18:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-cas-in-luminis/#comment-1743</guid>
		<description>This isn&#039;t exactly what we do in our environment.  In fact what you see in the function I wrote is primarily a series of calls to phpCAS functions which are all documented on their site.  There is a lot of additional complexity we&#039;ve coded in around this.  As I said in the post, this is &quot;merely a starting point for people interested in this WebISO technology.&quot;</description>
		<content:encoded><![CDATA[<p>This isn&#8217;t exactly what we do in our environment.  In fact what you see in the function I wrote is primarily a series of calls to phpCAS functions which are all documented on their site.  There is a lot of additional complexity we&#8217;ve coded in around this.  As I said in the post, this is &#8220;merely a starting point for people interested in this WebISO technology.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ken</title>
		<link>http://nosheep.net/story/leveraging-cas-in-luminis/comment-page-1/#comment-1741</link>
		<dc:creator>ken</dc:creator>
		<pubDate>Wed, 29 Mar 2006 17:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://nosheep.net/story/leveraging-cas-in-luminis/#comment-1741</guid>
		<description>Are you confident that in exposing your CAS code you are not introducing any security holes for would be authenticators?</description>
		<content:encoded><![CDATA[<p>Are you confident that in exposing your CAS code you are not introducing any security holes for would be authenticators?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
