Zoomdata Version

Using OAuth 2.0 to Access Zoomdata

Zoomdata supports the OAuth 2.0 protocol for authentication and authorization as well as the OAuth 2.0 Implicit Workflow.

To configure OAuth 2.0 Implicit Workflow, you need to create a client identifier (Client ID) for your application in Zoomdata. When working with Zoomdata, your application requests an access token from Zoomdata. This access token is used to obtain access to Zoomdata resources.

Figure 1

Manage Client ID in Zoomdata

You can create, read, update, or delete the Client ID using Zoomdata's Public REST API.

Create Client ID

Before you begin, you must register your application in Zoomdata using the Public REST API.

If you need assistance to set up the Client ID in Zoomdata, contact Zoomdata Technical Support .

Access Token Request

Once your application is set up in Zoomdata, the user may send a request containing (1) the client ID, (2) a callback URL and other service parameters to Zoomdata. Zoomdata checks whether there are active sessions for that user. If not, the user must log in with appropriate credentials. Once the user is identified in Zoomdata (either via standard login or from an existing session), user consent is requested. By confirming your consent, you allow the client application to use Zoomdata resources on behalf of your Zoomdata account. Then, Zoomdata creates an access token for your client app with the same access rights for the corresponding user.

The Zoomdata service redirects the user to the specified callback URL in client app. The access token is provided as a request parameter.

Working with Zoomdata Using Obtained Access Token

Each time when the client app requests resources from the Zoomdata server, an access token is sent and corresponding resources are returned to the app.