<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Authenticating a login</title>
	<atom:link href="http://nicktelford.net/2010/06/21/authenticating-a-login/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicktelford.net/2010/06/21/authenticating-a-login/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 21 Jun 2010 22:09:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Curd</title>
		<link>http://nicktelford.net/2010/06/21/authenticating-a-login/comment-page-1/#comment-90</link>
		<dc:creator>Peter Curd</dc:creator>
		<pubDate>Mon, 21 Jun 2010 22:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://nicktelford.net/?p=47#comment-90</guid>
		<description>I agree entirely - the &quot;logging in&quot; system for an application should be exactly as you describe, an &quot;Authentication&quot; phase followed by a background &quot;Authorisation&quot;.

These days, most web based systems could replace login with email - although there is some problem there with emails changing and display names not.. I like the below system:

Old Name    - Replaced with
&quot;username&quot; = &quot;email address&quot; (or &quot;e-mail address&quot;, never &quot;e mail address&quot;)
&quot;password&quot; = &quot;pass phrase&quot; (password is also a compound noun)
&quot;login&quot; as in the process = &quot;Authentication&quot;
&quot;user id&quot;/&quot;nickname&quot; = &quot;Display Name&quot;

But it confuses people so we stick with username, password and nickname etc.

In a business world, fitting with other apps is often more important than good grammar.  If a customer wants to &quot;login&quot; not &quot;authenticate&quot; then that&#039;s what they get.  If a user wants &quot;primary securing identity key&quot; I&#039;m sure they&#039;d get that too.</description>
		<content:encoded><![CDATA[<p>I agree entirely &#8211; the &#8220;logging in&#8221; system for an application should be exactly as you describe, an &#8220;Authentication&#8221; phase followed by a background &#8220;Authorisation&#8221;.</p>
<p>These days, most web based systems could replace login with email &#8211; although there is some problem there with emails changing and display names not.. I like the below system:</p>
<p>Old Name    &#8211; Replaced with<br />
&#8220;username&#8221; = &#8220;email address&#8221; (or &#8220;e-mail address&#8221;, never &#8220;e mail address&#8221;)<br />
&#8220;password&#8221; = &#8220;pass phrase&#8221; (password is also a compound noun)<br />
&#8220;login&#8221; as in the process = &#8220;Authentication&#8221;<br />
&#8220;user id&#8221;/&#8221;nickname&#8221; = &#8220;Display Name&#8221;</p>
<p>But it confuses people so we stick with username, password and nickname etc.</p>
<p>In a business world, fitting with other apps is often more important than good grammar.  If a customer wants to &#8220;login&#8221; not &#8220;authenticate&#8221; then that&#8217;s what they get.  If a user wants &#8220;primary securing identity key&#8221; I&#8217;m sure they&#8217;d get that too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

