OAuth 2.0: An Overview
Why Stack Overflow recommends it
Stack Overflow users link it as a quick, high-level primer on how OAuth 2.0 flows work when answering or asking questions about authorization grants, tokens and add-on authentication.
Recommended by 2 people across 4 different months, 2017 to 2018.
What it is
A short vendor-produced explainer from InterSystems Learning Services that introduces OAuth 2.0, covering why the technology is useful and the basic flow between client, authorization server and resource server. It is a general overview rather than a product-specific tutorial.
What people said
Recommends TheAddonDepot · 2017-08 · Stack Overflow · on “Writing file to Application Data Folder on Add-ons from Google App Script server code”
Users have to explicitly grant your Add-on access to the private AppData folder. And currently that's only achievable by setting up an OAuth2 flow. EDIT As of November 2017, Apps Script now supports explicit OAuth scopes. There is no longer a need to set up a custom OAuth flow, simply set the desired OAuth scope in the manifest file (as documented here [LINK] ) to request access to a user's App Data Folder. Here's a video that provides a good overview of how OAuth2 works (independent of Apps Script) OAuth 2.0: An Overview [this video] If you're up to the task, you can review Google's OAuth2 documentation [LINK] and figure out how to implement it for your use case, but you're better off leveraging
Recommends TheAddonDepot · 2018-06 · Stack Overflow · on “Return a parameter in Google App Script callback”
You cannot change the value nor decode the state string. That would defeat the purpose of having an OAuth2 flow in the first place - a secure reliable method to authenticate users and authorize applications on their behalf. You should check out this video (linked below) it will explain the process behind oauth2 flows better than I can: [this video]
Recommends TheAddonDepot · 2018-09 · Stack Overflow · on “Issue with Gmail addon needing dynamic auth url”
Not to sound condescending but I get the feeling that you don't fully grasp how oauth2 flows are meant to work. I'm guessing you've been tasked with implementing an OAuth2 flow for a CRM. So you might want to start with the specs as detailed here [LINK] . If you need a good high-level overview of an OAuth2 workflow I recommend watching the following video Workflow of Auth 2.0 [this video]
Recommends lauksas · 2018-11 · Stack Overflow · on “HTTP/1.1 401 Unauthorized error when calling HttpGet with OAuthConsumer client”
Not enough information to answer correctly, but seems that you are not getting the authentication header as you should. You first need to hit the oAuth URL, get you header then include it in the actual request. OAuth is different than Basic authentication, you need to authenticate prior to the request and carry the authentication token as long as it is valid. Quick video explaining the basics: [this video]
Cites stackjlei · 2017-10 · Stack Overflow · on “Why do you need authorization grant when you can just give the token out directly?”
Watching this video [this video] , it details in OAuth2 that the client application first has to get the authorization grant from the Authorization server and then use that grant to get a token before being able to access the resource server. What purpose does the grant serve? Why not give the client the token right away after the user signs on with his/her username and password?
Cites Luis Souza · 2018-07 · Stack Overflow · on “How to get a authentication code / token using Authlib 2.0 on Flask?”
I have read part of the documentation of Authlib [LINK] and the example [LINK] multiple times, I also have read articles about the concept of Auth 2.0 [LINK] , but I can't figure out how to do it. I want my user to make login (Using username and password) and then my application to return a token. After that the user can use the private resources @require_oauth('profile') . My client : *************************** 1. row *************************** client_id: wmahDfsran1jk6CaH1knpi3n client_secret: mnr4j15pZurBPYHq4KW4LY8HC7pS4TwjzMlJAUGmo7Bpy5gP issued_at: 1531271519 expires_at: 0 redirect_uri: [LINK] token_endpoint_auth_method: client_secret_basic grant_type: authorization_code password res