Are you able to specify a dynamic return URL with LinkedIn's API? If so, you can:
Generate a unique ID for each user (maybe even user.pk) Use this data in the return URL (e.g. example.com/oauth_return/ <unique_id>/) Attach that URL to a view which looks up the unique ID - you can now associate the user with the data returned by LinkedIn I do something similar with a different oAuth provider, and it works quite nicely. On May 21, 2:45 am, CrabbyPete <pete.do...@gmail.com> wrote: > I am trying to update a user profile of an existing user with a > LinkedIn profile. My problem is I need an email address, but LinkedIn > does not give you that information. So I have a user create an account > with their email address and ask if they want to link their profile to > their LinkedIn profile. The problem is that the way Oauth works is > that it uses a call back and there is no way to link the user who > initiated the Oauth call to the call back coming from LinkedIn. If you > look at the request.user its Anonymous. > > Does anyone have an idea how to get around this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
