This now works. I can pass the email address in place of screen name.
On Oct 5, 2:28 pm, Tom van der Woerdt <[email protected]> wrote: > I just did a quick check in my own application, it failed. So, unless > Taylor, Matt or John says otherwise, you should consider the definite > answer to be a No. > > Tom > > On 10/5/10 11:25 PM, Gary wrote: > > > Hi Tom, > > > These are thebasestrings with fictitious username, password and > > consumer key and so they will not pass through the validator. I have > > checked the actualbasestrings and they check-out ok. > > > Anyway, what I'm looking for is a definite yes or no as to whether > >emailaddresses-login is supported or not. Is there somewhere I could > > get this info? > > > Thanks, > > Gary > > > On Oct 5, 12:27 pm, Tom van der Woerdt <[email protected]> wrote: > >> Those aren'tbasestrings. > > >> Use the OAuthBaseString validator @ <http://quonos.nl/oauthTester/> > > >> By the way: I'm not sure about logging in with E-Mail addresses. It may > >> work, and it may not. > > >> Tom > > >> On 10/5/10 8:27 PM, Gary wrote: > > >>> Hi, > > >>> I'm also having this problem. I cannot login using the user'semail. > >>> AFAIK, I am encoding according to the documentation. I encode the > >>> post body and then encode again when I create thesignaturebase > >>> string. > > >>> Assume: > >>> screen name: myscrname > >>> password: m...@password <--- note I added @ to the password just > >>> to see if there was something about @ which was causing the problem > >>>email: [email protected] > > >>> ======================================= > >>> Using the screen name to login works fine: > > >>> Post body > >>> --------------- > >>> x_auth_mode=client_auth&x_auth_password=my > >>> %40password&x_auth_username=myscrname > > >>> Sigbasestring > >>> ---------------------- > >>> oauth_consumer_key%3Daaaaaaaaaaaaaaaaaaaaa%26oauth_nonce > >>> %3D3u988u37Acy3GkQWd6tJKrY3fPTefe2QYIL2WXb1R3gWP > >>> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp > >>> %3D1286237702%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth > >>> %26x_auth_password%3Dmy%2540password%26x_auth_username%3Dmyscrname > > >>> ======================================= > >>> Using theemailto login fails: > > >>> Post body > >>> --------------- > >>> x_auth_mode=client_auth&x_auth_password=my > >>> %40password&x_auth_username=me%40somewhere.com > > >>> Sigbasestring > >>> ---------------------- > >>> oauth_consumer_key%3Daaaaaaaaaaaaaaaaaaaaa%26oauth_nonce > >>> %3Dwwsim7hj1bfMylHARpmLwQerWjJJu4Y7kgzz8jCdY3Cv6%26oauth_signature_method > >>> %3DHMAC-SHA1%26oauth_timestamp%3D1286237782%26oauth_version > >>> %3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy%2540password > >>> %26x_auth_username%3Dme%2540somewhere.com > > >>> On Aug 30, 7:17 am, Taylor Singletary <[email protected]> > >>> wrote: > >>>> Hi Joe, > > >>>> Emailcan be accepted, as long as it is properly encoded. A URL encoded > >>>> POST > >>>> body by definition means that you'll already have to escape characters > >>>> like > >>>> the "@" symbol for your POST body -- then for yoursignaturebasestring, > >>>> it'll have to be encoded again. > > >>>> Most Twitter users sign in with their screen name and password. Do you > >>>> have > >>>> a use case where users are predominantly using theiremailaddress? > > >>>> Taylor > > >>>> On Mon, Aug 30, 2010 at 1:10 AM, joe <[email protected]> wrote: > >>>>> Hi guys, > > >>>>> I have a question about getting access token. > >>>>> Can I useemailaddress as the username? When x_auth_username = > >>>>> "[email protected]", always a error msg returned: "Failed to validate oauth > >>>>> signatureand token". But if user input username, there is no problem > >>>>> at all. > >>>>> So can anybody tell whetheremailaddress is accepted? Thanks a lot. > > >>>>> Joe > > >>>>> -- > >>>>> Twitter developer documentation and resources:http://dev.twitter.com/doc > >>>>> API updates via Twitter:http://twitter.com/twitterapi > >>>>> Issues/Enhancements Tracker: > >>>>>http://code.google.com/p/twitter-api/issues/list > >>>>> Change your membership to this group: > >>>>>http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
