<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Zend_Auth and more than one record matches the supplied identity</title>
	<link>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity</link>
	<description>A lot to do about nothing</description>
	<pubDate>Fri, 30 Jul 2010 10:06:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Zend_Auth and more than one record matches the supplied identity by: Administrator</title>
		<link>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-63246</link>
		<pubDate>Wed, 14 Jul 2010 20:17:46 +0000</pubDate>
		<guid>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-63246</guid>
					<description>@Rolando - nice, that's a clean way to have a non-unique identity.</description>
		<content:encoded><![CDATA[	<p>@Rolando - nice, that&#8217;s a clean way to have a non-unique identity.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Zend_Auth and more than one record matches the supplied identity by: Rolando</title>
		<link>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-63176</link>
		<pubDate>Tue, 13 Jul 2010 20:34:29 +0000</pubDate>
		<guid>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-63176</guid>
					<description>I had the same  issue but instead of doing something like 

$result  = $auth-&amp;#62;authenticate($adapter);
if($result-&amp;#62;isValid()){....

Im using this expression

if($result-&amp;#62;getCode() == Zend_Auth_Result::SUCCESS &amp;#166;&amp;#166; $result-&amp;#62;getCode() == Zend_Auth_Result::FAILURE_IDENTITY_AMBIGUOUS){...

This allowed me to have ambigous identity, which wouldnt hurt since credential is unique.</description>
		<content:encoded><![CDATA[	<p>I had the same  issue but instead of doing something like </p>
	<p>$result  = $auth-&gt;authenticate($adapter);<br />
if($result-&gt;isValid()){&#8230;.</p>
	<p>Im using this expression</p>
	<p>if($result-&gt;getCode() == Zend_Auth_Result::SUCCESS || $result-&gt;getCode() == Zend_Auth_Result::FAILURE_IDENTITY_AMBIGUOUS){&#8230;</p>
	<p>This allowed me to have ambigous identity, which wouldnt hurt since credential is unique.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Zend_Auth and more than one record matches the supplied identity by: Roger G.</title>
		<link>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-54962</link>
		<pubDate>Sat, 13 Feb 2010 18:38:05 +0000</pubDate>
		<guid>http://www.robertbolton.com/zend_auth-and-more-than-one-record-matches-the-supplied-identity#comment-54962</guid>
					<description>Thanks for the heads up. I was having the same problem. I ended up reversing the two fields, since security wasn't too much of a concern. It is a basic community site where people have to enter in their last name and password in lieu of a username. Since multiple people have the same last name, it was returning false. So I just treated the password as the username field, and the last name as the password, so there are no duplicates. Not sure if this is wise, but the site is very basic and only allows people to post comments when logged in (i.e. no sensitive information is stored).</description>
		<content:encoded><![CDATA[	<p>Thanks for the heads up. I was having the same problem. I ended up reversing the two fields, since security wasn&#8217;t too much of a concern. It is a basic community site where people have to enter in their last name and password in lieu of a username. Since multiple people have the same last name, it was returning false. So I just treated the password as the username field, and the last name as the password, so there are no duplicates. Not sure if this is wise, but the site is very basic and only allows people to post comments when logged in (i.e. no sensitive information is stored).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
