Creating a New OAuth2 Connection

To create a connection to a Google, Allegro, or similar account, choose the Open Authentication type and click New…

In OAuth2 authentication, access to a resource that has an owner (and is protected by an authorization system) is granted to the client by the resource owner through an authorization server.

In the simplest case, the process of granting the client access rights to the owner's resources works as follows:

1. The client (the OAuth2 application) requests the authorization server to grant access to the owner's resource within a specified scope.
2. To grant permissions, the owner logs in to the authorization server using their account.
3. The server then displays information about which client is requesting access and what scope of permissions it is asking for.
4. The resource owner decides whether to grant or deny the requested permissions.
5. Confirming the permissions means giving the client consent to act on behalf of the resource owner within the scope approved by the owner.
6. The client requests a token from the server to use during communication with the resource server.
7. The server returns an access token and a refresh token to the client.
8. The client obtains access to the owner's resources within the granted scope.

The resources made available to the application are the resources of the owner who logs in to their account on the authorization server.

In the GRAVITY system, authorization through an OAuth2 server requires providing the following information:

• Name → a unique name for the connection being created.
• Authorization server → the authorization server you intend to use, which is equivalent to selecting the resource server, e.g., Google, Dropbox, OneDrive, Allegro, etc.
• AppClientId and AppSecretKey → the client application's identifiers; this key pair allows the authorization server to identify the client requesting access to resources.
• RedirectUrl → the callback address to which the authorization server will redirect after successful authorization. Here, you must provide the available local ports that you have designated to handle the callback, separated by commas.

When you have correctly filled in the fields required to start the authentication process, the Sign in with G button becomes active. By clicking it, you will be redirected to a web browser, where you complete the process of granting permissions to the client application.

The process shown for the Google authorization server:

1. Sign in to the Google account whose resources you intend to make available.

2. After signing in, you will be asked to grant permissions to the Google application represented by the AppClientId and AppSecretKey used in the connection.

3. Confirm the scope within which the application may act on your behalf and click Continue. You will see a message confirming that the permissions were successfully granted, and you can return to the GRAVITY application.

4. After returning to the GRAVITY system, the fields related to the user who granted access to their resources for the created connection will be populated.

A single client application may hold authorization credentials for resources belonging to multiple users.

Clicking the Test button after a successful login allows you to verify the connection.