<?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"
	>
<channel>
	<title>Comments on: SaaS and the Case for Single Sign-On</title>
	<atom:link href="http://www.adeptechllc.com/2008/02/14/saas-and-the-case-for-single-sign-on/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adeptechllc.com/2008/02/14/saas-and-the-case-for-single-sign-on/</link>
	<description>Software, Process and Security</description>
	<pubDate>Wed, 07 Jan 2009 10:12:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Peter H Coffin</title>
		<link>http://www.adeptechllc.com/2008/02/14/saas-and-the-case-for-single-sign-on/#comment-91</link>
		<dc:creator>Peter H Coffin</dc:creator>
		<pubDate>Fri, 15 Feb 2008 02:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/2008/02/14/saas-and-the-case-for-single-sign-on/#comment-91</guid>
		<description>Heck, employees want SSO. All those bullet-tick requirements for passwords, combined with an ever-increasing number of things wot want authentication means that some employees will spend literally hours several times a year just changing passwords, and (the worst of all possible sins) writing them down as there's no possibly way to remember 20 different passwords on different systems and applications, some of which may not have been touched since the LAST password dance. As a wild guess, any corporation that can manage to roll ALL of its authentication into a single system will probably end up saving at least a man-day &lt;em&gt;per employee&lt;/em&gt; of time spent otherwise dealing with passwords, including remembering, resetting, changing and updating password-related documentation.</description>
		<content:encoded><![CDATA[<p>Heck, employees want SSO. All those bullet-tick requirements for passwords, combined with an ever-increasing number of things wot want authentication means that some employees will spend literally hours several times a year just changing passwords, and (the worst of all possible sins) writing them down as there&#8217;s no possibly way to remember 20 different passwords on different systems and applications, some of which may not have been touched since the LAST password dance. As a wild guess, any corporation that can manage to roll ALL of its authentication into a single system will probably end up saving at least a man-day <em>per employee</em> of time spent otherwise dealing with passwords, including remembering, resetting, changing and updating password-related documentation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
