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 client identifier (Client ID) for your application in Zoomdata. When working with Zoomdata, your application will request 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.

Documentation about implementing OAuth2 security with Zoomdata is coming soon.

Create Client ID

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

Access Token Request

On this step your app sends request containing client ID, callback URL, and other service parameters.

Zoomdata will check if there are any active sessions for the user who is going to access Zoomdata. If there are no active sessions, the Login page will be displayed asking the credentials. If there is an active session in Zoomdata, user consent will be requested.

After you have specified your Zoomdata credentials, the user consent is requested.

By confirming your consent, you allow your client application to use Zoomdata resources on behalf of your Zoomdata account.

After this, Zoomdata will create an access token for your client app with the same access rights for the corresponding user.

Zoomdata server will redirect the user to the specified callback URL in client app. The access token will be 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 will be returned to the app.