Cmdlets for DigitalOcean

Build 20.0.7587

Using OAuth Authentication

OAuth requires the authenticating user to interact with DigitalOcean using the browser. The cmdlet facilitates this in various ways as described below.

Embedded Credentials

Desktop Applications

See Embedded Credentials to connect with the cmdlet's embedded credentials and skip creating a custom OAuth app.

Headless Machines

See Headless Machines to skip creating a custom OAuth app and authenticate an application running on a headless server or another machine where the cmdlet is not authorized to open a browser.

Custom Credentials

Instead of connecting with the cmdlet's embedded credentials, you can register an app to obtain the OAuthClientId and OAuthClientSecret.

When to Create a Custom OAuth App

Desktop Applications

Creating a custom OAuth app is optional as the cmdlet is already registered with DigitalOcean and you can connect with its embedded credentials. You might want to create a custom OAuth app to change the information displayed when users log into the DigitalOcean OAuth endpoint to grant permissions to the cmdlet.

Headless Machines

Creating a custom OAuth app is optional to authenticate a headless machine; the cmdlet is already registered with DigitalOcean and you can connect with its embedded credentials. In the headless OAuth flow, users need to authenticate via a browser on another machine. You might want to create a custom OAuth app to change the information displayed when users log into the DigitalOcean OAuth endpoint to grant permissions to the cmdlet.

Creating a Custom OAuth App

See Creating a Custom OAuth App for a procedure.

Copyright (c) 2020 CData Software, Inc. - All rights reserved.
Build 20.0.7587