Shade,<div><br></div><div>Correct. If no positive assertion can be discovered, the Login link remains so the user can provide their identifier (perhaps seeing the last one they entered) and begin a checkid_setup flow. </div>
<div><br></div><div>If a positive assertion is found, it would make sense in some scenarios to still allow the user to choose to log in normally rather than auto-login (perhaps to explicitly choose a different identifier). </div>
<div><br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
<br><br><div class="gmail_quote">On Mon, Jul 13, 2009 at 1:31 PM, SitG Admin <span dir="ltr"><<a href="mailto:sysadmin@shadowsinthegarden.com">sysadmin@shadowsinthegarden.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the client finds it gets a positive assertion, it changes or adds to the "Login" link UI a message like "(auto-login now)", which forwards the positive assertion to the server for processing and logs the user in without any further interaction.<br>
</blockquote>
<br></div>
And if the assertion is negative or some other noncommittal equivalent to "we can't say at this time whether that user has an account with us", you still have that text field for them to type in the OP they wish to use, "automatically" or not?<br>
<br>
-Shade<br>
</blockquote></div><br></div>