Some of these questions may be basic. Be gentle. I've been reading all
the articles and going through examples for oauth and openid, and I
could use a sounding board to make sure I'm understanding it all.

I'm building a python web app (let's call it myapp) that I would like
to use to interact with the linkedin api.

First, as I understand, the OAuth service (http://code.google.com/
appengine/docs/python/oauth/overview.html) is not appropriate here...
that service is about allowing myapp to serve as an oauth provider.
But in this case I want to be an oauth consumer, so that service
doesn't sound like it will help me.

So I could use some python library that allows me to do oauth with
linkedin, like this one: http://code.google.com/p/python-linkedin/

Now as I understand, oauth wouldn't make much sense unless the user
has already logged in somehow. I just get credentials returned... but
nothing gets stored as a cookie so I know that "this" user goes with
"these" credentials. So I should probably already have the user login
somehow (like with openid) and then store those credentials on the
user record (or on a model that extends the user, like UserProfile or
something).

So if I wanted to use LinkedIn for openid, it's a two-step process.
First, I show the user the linkedin login button, take them through
the openid process for linkedin, and then I need to separately ask
them to go through the oauth process to authorize myapp to work with
their account on linkedin.

Is that right? There's no way to do this with just one step?

And DOES linkedin act as an openid provider? If so, what is their
provider URL? I've looked but cannot find it.

Please let me know if I'm off-base with any of my assumptions.

Thanks!
Bob

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to