[geeklog-devel] Twitter OAuth for Geeklog

[今駒哲子@Geeklog IvyWe]

Hi Tom,


> I received the Twitter Direct message now. Makes sense that it wouldn't have

> sent it before since I already had an account on Geeklogjp.


Congratulations!


> Facebook also worked now. It grabbed my Name, email and photo. Any chance of

> grabbing bio and location information like you did in Twitter?


http://developers.facebook.com/docs/reference/api/user
All of these data can be get.
Email is included.


> What is the reason behind why in Twitter and LinkedIn OAuth methods you

> don't retrieve the email address (I assume there is a problem since you

> retrieve it in Facebook)?


1. Twitter API:
http://dev.twitter.com/doc/get/users/suggestions/:slug
id
name
screen_name
location
description
url
time_zone
created_a
profile_image_url
friends_count
followers_count
favourites_count
statuses_count

Email is not included...


2. LinkedIn[Profile API]

Default Fields Returned
http://developer.linkedin.com/docs/DOC-1002
 ... first-name,last-name,headline,site-standard-profile-request/url

More
http://developer.linkedin.com/docs/DOC-1014
 ... id,first-name,last-name,picture-url,headline,summary,positions,educations

Email is not included...



> Great Work by the way.


Thanks!


2010/8/17 Tom <websitemaster at cogeco.net>:

> Hi Ivy,

>

> I received the Twitter Direct message now. Makes sense that it wouldn't have

> sent it before since I already had an account on Geeklogjp.

>

> Facebook also worked now. It grabbed my Name, email and photo. Any chance of

> grabbing bio and location information like you did in Twitter?

>

> What is the reason behind why in Twitter and LinkedIn OAuth methods you

> don't retrieve the email address (I assume there is a problem since you

> retrieve it in Facebook)?

>

> Great Work by the way.

>

> Tom

> -----Original Message-----

> From: geeklog-devel-bounces at lists.geeklog.net

> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ????@Geeklog

> IvyWe

> Sent: August-17-10 2:48 AM

> To: Geeklog Development

> Subject: Re: [geeklog-devel] Twitter OAuth for Geeklog

>

> Hi Tom,

>

> Twitter OAuth in Geeklog:

>

> Your Twitter setting is okey.

> I tried again, but I get password message, correctry.

>

>  ivyjp: Your account via Twitter OAuth has been created

> successfully.http://is.gd/eiMk2 If you wantto edit your account, use

> the password bellow. password: 7ef68e2e

>

> This message is from myself.

> So secure.

>

> I removed your account via Twitter,  so try again, please.

>

>

> Facebook OAuth in Geeklog:

>

> I changed fb to gl17x in Facebook application's connection, now.

> So try again, please.

>

>

> Ivy

> --

> http://www.ivywe.co.jp

> http://www.geeklog.jp

>

> from iPad

>

>

> 2010/8/17, Tom <websitemaster at cogeco.net>:

>> Hi Ivy,

>>

>> I was able to log in via LinkedIn and all seemed fine. Is there currently

> no

>> way to get a password to the user?

>>

>> With Twitter, I went to my Twitter Account -> Settings -> Connections

>> I saw no way of removing the Geeklogjp connection. I could only revoke

>> access, which I did. I then logged back into your Geeklog site using

>> Twitter. Twitter asked me if it should allow access again which I said ok.

>> All seems fine, my Geeklog account is updated with my new Twitter

>> information. Checking in the Connections tab on Twitter, Geeklogjp does

> now

>> have read and write access.  The only thing is, I still (after about 10

>> minutes) do not have a direct message with a password.

>>

>> With Facebook, I didn't get very far. Clicking on the Facebook Login

> button,

>> it brought me to a Facebook page asking if it should give Geeklogjp access

>> to my information (this was in Internet Explorer 8 and I was already

> logged

>> into Facebook). I clicked Allow and then for some reason the File Download

>> form came up and then an Internet Explorer error message came up saying

>> cannot download. I figured this may be a Internet Explorer "thing" so I

> then

>> tried Google Chrome. Clicking on the Login button brought me to the

> Facebook

>> login page. When I attempted to login I got the following error message.

>>

>> {

>>    "error": {

>>       "type": "OAuthException",

>>       "message": "Invalid redirect_uri: The Facebook Connect cross-domain

>> receiver URL (http://gl17x.hiroron.com/users.php?oauth_login=facebook)

> must

>> have the application's Connect URL (http://fb.hiroron.com/) as a prefix.

>> You can configure the Connect URL in the <a

>>

> href=\"http://www.facebook.com/developers/editapp.php?app_id=131898813520219

>> \">Application Settings Editor</a>."

>>    }

>> }

>>

>> It looks like Facebook doesn't like the different domain prefix.

>>

>> Let me know when you want me to test logging in again.

>>

>> Thanks

>>

>> Tom

>>

>> -----Original Message-----

>> From: geeklog-devel-bounces at lists.geeklog.net

>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of ????@Geeklog

>> IvyWe

>> Sent: August-16-10 12:06 PM

>> To: Geeklog Development

>> Subject: Re: [geeklog-devel] Twitter OAuth for Geeklog

>>

>> Tom,

>>

>>> I see that your development site now has Facebook and LinkedIn login

>>> buttons.  How is development going and when do you expect to release it

> (I

>>> hope!) ?

>>

>> Today, we finished.

>> Please test Twitter Facebook LinkedIn OAuth in Geeklog!

>> http://gl17x.hiroron.com/

>>

>> Now we are writing documents.

>>

>> (1)

>> Twitter OAuth: Username and other are set. e-mail is not set but

>> Geeklog send password by Twitter direct message.

>> So the user can edit account.

>>

>> Tom, please set off Twitter Geeklogjp application(read only) in settings.

>> And try OAuth via Twitter, then Geeklogjp application(read and write)

>> will appear in settings.

>> You will get direct message.

>>

>> (2)

>> via Facebook OAuth: Username, e-mail and other are set. Password is not

> set.

>>

>> (3)

>> via LinkedIn OAuth: Username and other without e-mail. Password is not

> set.

>>

>> We will release Aug. 18 or 19 may be.

>>

>>

>> Files:

>>   language/english.php

>>   language/japanese_utf-8.php

>>   system/lib-security.php

>>   system/classes/oauthhelper.class.php (+)

>>   system/classes/oauth/twitter.auth.class.php (+)

>>   system/classes/oauth/facebook.auth.class.php (+)

>>   system/classes/oauth/linkedin.auth.class.php (+)

>>

>> add to PEAR

>>   system/pear/Net/URL2.php (+)      <- Net_URL2-0.3.1

>>   system/pear/HTTP/Request2.php (+) <- HTTP_Request2-0.5.2

>>   system/pear/HTTP/Request2/* (+)   <- HTTP_Request2-0.5.2

>>   system/pear/HTTP/OAuth.php (+)    <- HTTP_OAuth-0.1.18

>>   system/pear/HTTP/OAuth/* (+)      <- HTTP_OAuth-0.1.18

>>

>> Public_html

>>   public_html/lib-common.php

>>   public_html/users.php

>>   public_html/images/sign-in-with-twitter.png (+)

>>   public_html/images/sign-in-with-twitter-sm.png (+)

>>   public_html/images/sign-in-with-facebook.png (+)

>>   public_html/images/sign-in-with-linkedin.png (+)

>>

>> Theme

>>   public_html/layout/professional/loginform.thtml

>>   public_html/layout/professional/loginform_oauth.thtml (+)

>>   public_html/layout/professional/users/loginform.thtml

>>

>> Author: @wkyhiroron

>> Presented by IVYWE and Winkey

>>

>> bye, Ivy

>>

>> --

>> http://www.geeklog.jp

>> http://www.ivywe.co.jp

>>

>> 2010/8/17 Tom <websitemaster at cogeco.net>:

>>> I see that your development site now has Facebook and LinkedIn login

>>> buttons.  How is development going and when do you expect to release it

> (I

>>> hope!) ?

>>>

>>> Thanks

>>>

>>> Tom

>>>

>>> -----Original Message-----

>>> From: geeklog-devel-bounces at lists.geeklog.net

>>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of hiroron

>>> Sent: August-05-10 6:40 AM

>>> To: geeklog-devel at lists.geeklog.net

>>> Subject: [geeklog-devel] Twitter OAuth for Geeklog

>>>

>>>

>>> Hi,

>>> Twitter OAuth for Geeklog is under development.

>>> Everyone try to login with "Sign in with Twitter" button at

>>> http://gl17x.hiroron.com/.

>>> Your feedback is highly appreciated.

>>> No problem found so far at Japanese environment.

>>>

>>> Easier user login method for community site by Geeklog.

>>>

>>> bye, hiroron

>>> --

>>> http://hiroron.com/

>>>

>>>

>>> _______________________________________________

>>> geeklog-devel mailing list

>>> geeklog-devel at lists.geeklog.net

>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>>>

>>> __________ Information from ESET NOD32 Antivirus, version of virus

>> signature

>>> database 5342 (20100805) __________

>>>

>>> The message was checked by ESET NOD32 Antivirus.

>>>

>>> http://www.eset.com

>>>

>>>

>>>

>>>

>>>

>>> __________ Information from ESET NOD32 Antivirus, version of virus

>> signature

>>> database 5370 (20100816) __________

>>>

>>> The message was checked by ESET NOD32 Antivirus.

>>>

>>> http://www.eset.com

>>>

>>>

>>> _______________________________________________

>>> geeklog-devel mailing list

>>> geeklog-devel at lists.geeklog.net

>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>>>

>> _______________________________________________

>> geeklog-devel mailing list

>> geeklog-devel at lists.geeklog.net

>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>>

>> __________ Information from ESET NOD32 Antivirus, version of virus

> signature

>> database 5371 (20100816) __________

>>

>> The message was checked by ESET NOD32 Antivirus.

>>

>> http://www.eset.com

>>

>>

>>

>>

>> __________ Information from ESET NOD32 Antivirus, version of virus

> signature

>> database 5371 (20100816) __________

>>

>> The message was checked by ESET NOD32 Antivirus.

>>

>> http://www.eset.com

>>

>>

>> _______________________________________________

>> geeklog-devel mailing list

>> geeklog-devel at lists.geeklog.net

>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>>

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>

> __________ Information from ESET NOD32 Antivirus, version of virus signature

> database 5372 (20100817) __________

>

> The message was checked by ESET NOD32 Antivirus.

>

> http://www.eset.com

>

>

>

>

> __________ Information from ESET NOD32 Antivirus, version of virus signature

> database 5372 (20100817) __________

>

> The message was checked by ESET NOD32 Antivirus.

>

> http://www.eset.com

>

>

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

>