No. In the case of manual entry, the entire user experience is tricky and it would be much better for the client to use its own simple server which will get the information and display it to the user. That was it can use any terms it wants.
EHL On 6/7/09 2:28 PM, "Andrew Arnott" <andrewarn...@gmail.com> wrote: > Can we add to the 1.0a spec the exact term by which the verifier code should > be referred to by the SP and Consumer? I know there are multiple languages > potentially involved and this can't be done for all of them, but if the > Consumer is asking the user to type in the "verification code" and the SP has > told the user "here is the verifier", that could potentially be confusing. > Can we get a suggestion in the spec that everyone refer to it as the > "verification code" or something consistent at least, so that the user can > easily see that the two refer to the same thing? (this only matters when user > involvement is required in the verification entry). > > -- > Andrew Arnott > "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 > > > On Tue, May 12, 2009 at 4:10 PM, Eran Hammer-Lahav <e...@hueniverse.com> > wrote: >> >> Please review: >> >> http://oauth.googlecode.com/svn/spec/core/1.0a/drafts/3/oauth-core-1_0a.html >> >> Change log: >> >> http://code.google.com/p/oauth/source/diff?spec=svn997&old=994&r=997&format=u >> nidiff&path=%2Fspec%2Fcore%2F1.0a%2Foauth-core-1_0a.xml >> >> The changes are: >> >> 1. Changed draft designation from discussion to implementer. >> 2. Added author, added 'Editor' designation. >> 3. IMPACT: Added required response parameter 'oauth_callback_confirmed=true' >> in 6.1.2. >> 4. Language changes in 6.2.3 (no impact). >> 5. Moved Security Considerations appendix to new section 11. >> 6. Added three new security considerations: 11.14-16. >> >> * Deadline for feedback is May 25th. >> * This is expected to be the last draft. >> >> EHL >> >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
