Currently we use Delegation to authorize our web client to call our API on behalf of a user. Our basic flow is: 1- Client presents user with custom login page (we don’t use the Lock Widget, because of our business requirements). 2- Client POST request to /oauth/ro { "client_id”:”ID”, ”client…

Your basic client flow is the de-facto use case for APIs authentication . Basically you need to create a new API in the Dashboard => APIs section and use the base URL of your API server in the Identifier field. This will be reffered as Audience in your access_tokens. Please use RS256 as signing …

Now that delegation is being deprecated, which Authorization Flow should we use?

Get Help

mitchellwaynemorris November 15, 2017, 5:43pm 6

Yep, timely documentation for laymen like me would be most helpful. Or at least please respond and let me know where we are at in this process.

Topic		Replies	Views
Issue with delegation for a new client application Get Help delegation , layer	2	3889	March 2, 2018
Choice of authentication flow Get Help architecture , authentication , api-authorization , flow	5	4293	March 2, 2018
Understanding client_credentials flow in terms of identity Get Help client_credentials	3	4681	March 2, 2018
Client Credentials Flow for api acces Get Help	2	1193	October 5, 2022
Getting token via Resource Owner Password without client secret Get Help	8	8078	April 17, 2019

Now that delegation is being deprecated, which Authorization Flow should we use?

Related topics