<?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: Good example of BAD IdM practices</title>
	<atom:link href="http://eternallyoptimistic.com/2006/04/13/bad-pwd-mgmt/feed/" rel="self" type="application/rss+xml" />
	<link>http://eternallyoptimistic.com/2006/04/13/bad-pwd-mgmt/</link>
	<description></description>
	<lastBuildDate>Wed, 10 Aug 2011 17:44:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Don</title>
		<link>http://eternallyoptimistic.com/2006/04/13/bad-pwd-mgmt/comment-page-1/#comment-46</link>
		<dc:creator>Don</dc:creator>
		<pubDate>Thu, 13 Apr 2006 22:25:40 +0000</pubDate>
		<guid isPermaLink="false">https://eternaloptimist.wordpress.com/2006/04/13/bad-pwd-mgmt/#comment-46</guid>
		<description>If I may paraphrase, without all of the Web &amp; Identity stuff in there - and you know I will.

&quot;A program has a misleading, wrong or otherwise useless message; and the person on the help desk is clueless. And you are *surprised* ?&quot;

Respectfully, this is not an identity management problem it is basic software design problem. If the website had in an effort to protect you against yourself, politely, informed you that you long standing dictionary based password had been expired and that you should have a cryptographer generate you a new one (then kill the cryptographer - They are currently in season anyway). You would have no problem with it - and we would have a blog entry on something else. Basic software design techniques should have caught this problem that is where your criticism should go.

See you after your next flight.

&lt;em&gt;&lt;strong&gt;Pam says:&lt;/strong&gt;  of course you&#039;re right -- the only difference is that identity &amp; access management software exists to abstract this functionality away from general software design.   Even the simplest portal software can notify you and help you to change your password.  To mess up something so very well understood and commodotized is, to me, even dumber than messing up your site&#039;s regular content. &lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>If I may paraphrase, without all of the Web &amp; Identity stuff in there &#8211; and you know I will.</p>
<p>&#8220;A program has a misleading, wrong or otherwise useless message; and the person on the help desk is clueless. And you are *surprised* ?&#8221;</p>
<p>Respectfully, this is not an identity management problem it is basic software design problem. If the website had in an effort to protect you against yourself, politely, informed you that you long standing dictionary based password had been expired and that you should have a cryptographer generate you a new one (then kill the cryptographer &#8211; They are currently in season anyway). You would have no problem with it &#8211; and we would have a blog entry on something else. Basic software design techniques should have caught this problem that is where your criticism should go.</p>
<p>See you after your next flight.</p>
<p><em><strong>Pam says:</strong>  of course you&#8217;re right &#8212; the only difference is that identity &amp; access management software exists to abstract this functionality away from general software design.   Even the simplest portal software can notify you and help you to change your password.  To mess up something so very well understood and commodotized is, to me, even dumber than messing up your site&#8217;s regular content. </em></p>
]]></content:encoded>
	</item>
</channel>
</rss>

