Hi George,

xAuth does accept email addresses. Your POST body by definition needs to be
URL-escaped, and when you generate your signature base string that means
that you'll be URL encoding those URL-encoded values again.

Example POST body:
x_auth_mode=client_auth&x_auth_password=thisismypass&x_auth_username=someonesemail%
40address.com

Example base string:
POST&https%3A%2F%2Fapi.twitter.com
%2Foauth%2Faccess_token&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DgATtgiuYofyPwzUS32vwWDBxf43Y4cWvJLZ1NhMrYfI%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1271195706%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dthisismypass%26x_auth_username%3Dsomeonesemail%
2540address.com


Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Tue, Apr 13, 2010 at 2:30 PM, George McBay <g...@funxed.com> wrote:

> I'm converting a twitter client from basic auth to xauth and
> everything is working fine except I have been unable to generate an
> oAuth token using xauth if the user attempts to sign in with an email
> address instead of their Twitter username.
>
> Is a Twitter user's email address a valid value for an xAuth
> x_auth_username parameter?  And if so, is there anything about the
> encoding that's odd?  I've tried the various obvious forms of HTTP
> value escaping but with no luck so far.
>
> It would be really nice to see something like the access_token page's
> Example Signature Base String that uses an email address (if that is
> even supported?) successfully.
>
> Thanks in advance.
>
>
>


-- 
To unsubscribe, reply using "remove me" as the subject.

Reply via email to