Skip to content

Commit 8801aed

Browse files
author
hzoppetti
committed
added sentence with reference to authorization code flow and implicit flow
1 parent 4cc5ae5 commit 8801aed

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

openapi.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,8 @@ info:
5252
If you're designing an application that can authenticate with an arbitrary Linode user, then
5353
you should use the OAuth 2.0 workflows presented in this section.
5454

55+
The OAuth spec refers to the private and public workflows listed as the [authorization code flow](https://tools.ietf.org/html/rfc6749#section-1.3.1) and [implicit flow](https://tools.ietf.org/html/rfc6749#section-1.3.2).
56+
5557
For a more detailed example of an OAuth 2.0 implementation, see our guide on [How to Create an OAuth App with the Linode Python API Library](https://www.linode.com/docs/platform/api/how-to-create-an-oauth-app-with-the-linode-python-api-library/#oauth-2-authentication-exchange).
5658

5759
Before you implement OAuth in your application, you first need to create an OAuth client. You can do this [with the Linode API](https://developers.linode.com/api/v4/account-oauth-clients/#post) or [via the Cloud Manager](https://cloud.linode.com/profile/clients):

0 commit comments

Comments
 (0)