![]() ![]() GET oauth/authenticate is a replacement of Section 6.2 of the OAuth 1.0 authentication flow for applications using the callback authentication flow. ![]() Desktop applications must use this method (and cannot use GET oauth/authenticate). GET oauth/authorize fulfills Section 6.2 of the OAuth 1.0 authentication flow. Use the OAuth Request Token received in the previous step to redirect the user to authorize your developer App for access. GET oauth/authorize or GET oauth/authenticate:.Use this endpoint to get an OAuth Request Token, which then allows you to request user authorization. With the Twitter API, this 3-legged OAuth flow can be implemented using the following endpoints (see diagram and step-by-step example below): The IETF describes the 3-legged OAuth flow as “a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.” For example, if you authorize Medium to access your account, Medium will be able to post Tweets on your behalf (such as sharing an article to Twitter). In this case, your Twitter developer App. The client or third-party application.In this case, this is the Twitter user on behalf of whom you want to make an API request. ![]() The 3-legged OAuth flow (also sometimes referred to as “Sign-In With Twitter”) typically involves three parties: Note that user Access Tokens are uniquely generated for each single developer App in other words, if you generate an Access Token for App A, this specific Access Token would not work for App B. This is achieved via the 3-legged OAuth flow, during which you redirect a user to authorize your application and receive the user’s Access Token and Secret in exchange. To make a request on behalf of another user, you first need to obtain this user’s authorization. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |