Not signed in: If the user is not signed in on, they will be prompted to enter their credentials and grant access for the application to access their information on the same screen.After accepting the authorization request, the user will be redirected to the callback URL with a valid OAuth request token. Signed in but not approved: If the user is signed in to but has not approved the calling application, a request to share access with the calling application will be shown.The redirect to is not obvious to the user. Signed in and approved: If the user is signed in on and has already approved the calling application, they will be immediately authenticated and returned to the callback URL with a valid OAuth request token.The sign in endpoint will behave in one of three ways depending on the user’s status: Oauth_token_secret=veNRnAWe6inFuo8o2u8SLLZLjolYDmDP7SzL0YfYI& Oauth_token=NPcudxy0yU5T3tBzho7iCotZ3cnetKwcTIRlX0iwRl0& Your app should verify that oauth_callback_confirmed is true and store the other two values for the next steps.Įxample response (response body has been wrapped):Ĭache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 The body of the response will contain the oauth_token, oauth_token_secret, and oauth_callback_confirmed parameters. Any value other than 200 indicates a failure. Your app should examine the HTTP status of the response. Oauth_signature="F1Li3tvehgcraF8DMJ7OyxO4w9Y%3D", Oauth_consumer_key="cChZNFj6T5R0TigYB9yd1w", OAuth oauth_callback="http%3A%2F%2Flocalhost%2Fsign-in-with-twitter%2F", Example request (Authorization header has been wrapped):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |