Using web2py's sample classes as a reference and a lot of code written
by Ozgur Vatansever I have written code to OAuth into LinkedIn (built
on gluon.contrib.login_methods.oauth10a_account)
This enables access to a contact's name, job title, photo & company as
well as details about their connectio
I didn't.
But by doing the authentication manually (that is, in an interactive shell),
I was able to connect to linked in. I realized that I wouldn't be able to
get the information that I wanted though (email address - never provided by
linkedin!), so I gave up.
But the web2py linked-in aut
did you find a solution?
On Jun 26, 8:17 pm, Luis Goncalves wrote:
> One more clue:
>
> In the infinite loop, every loop through the linkedin "grant access"
> (/oas/oauth/authorize) page has a new oauth_token, such as
>
> https://www.linkedin.com/uas/oauth/authorize?oauth_token=f9eef16e-4f4...
One more clue:
In the infinite loop, every loop through the linkedin "grant access"
(/oas/oauth/authorize) page has a new oauth_token, such as
https://www.linkedin.com/uas/oauth/authorize?oauth_token=f9eef16e-4f45-4f5e-aa5f-82ab18ad3a16
L.
An update (getting closer, but still problems):
It seems there are a couple more errors in linkedin_account.py:
There is an extraneous command which must have been left over from sample
code:
profile = self.api.GetProfile(profile).public_url =
"http://www.linkedin.com/in/ozgurv";
5 matches
Mail list logo
