![]() ![]() In this post, I'll answer all these questions for you. For instance, you can post on LinkedIn on behalf of the user or populate their job application with the data from their LinkedIn profile.īut how do you integrate LinkedIn OAuth into your app? What are the steps you should follow? How do you get LinkedIn OAuth credentials? Is LinkedIn API free to use for adding OAuth to your app? Further, OAuth allows you to easily communicate with other apps. Your users can click a button and authenticate to your site using their LinkedIn accounts. Here's my code I'm using two views, one that redirects to the LinkedIn authorization page, and one for the return-url: from django.When was the last time you signed up to a website by entering your email and password? OAuth and social login have simplified the monotonous and traditional sign-up and log-in method. I've just 'discovered' your python-linkedin library earlier today and set it up and tried to make it work with Django.īut as soon as I set the authorization-code and want to retrieve the access-token with it, I get an LinkedInHTTPError : 401 Client Error: Unauthorized. This is currently blocking me, and I'm not quite sure how to proceed without getting down into the guts of the linkedin.py file. I would be very interested in hearing back from you on this if you could create a brand new app and test, and seeing an update to the README that clarifies the language a bit and includes updated sample app values that work as-is. I am curious if you might be testing this library with values from an app you created long ago as opposed to an app recently and, thus, experiencing the same troubles that I am? Intuition suggests that this is the case. The length/form of these values do not resemble at all my API Key/Secret from app1 (nor do they resemble your values from the README.md.) Regardless of which combination of these values that I use, the OAuth flow always results in a 401 error. However, when I create a new app (what I will call app2), I see that I now have an "API Key" a "Secret Key" as well as an "OAuth User Token" and "OAuth User Secret". An important detail here is that the length and form of my API Key/Secret values resemble the same ones you use in the README.md as well. When I follow the OAuth flow with the "API Key" and "API Secret" from an app I created a couple of years ago (what I will call app1) and plug them into the flow as what you describe in the README.md as "application key" and "application secret", everything works fine. ![]() I am finding a peculiar thing when using this library that I think may reflect an important bug, and I'd like your thoughts on it. The Invitation API allows your users to invite people they find in your application to their LinkedIn network. You can simply use the 4 credentials that are provided to you in your LinkedIn appliation as part of an OAuth 1.0a flow and immediately access your data. To connect to LinkedIn as a developer or just to access your own data, you don't even have to implement an OAuth 2.0 flow that involves redirects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |