CloudBeaver Documentation

DOWNLOAD pdf

Anonymous Access Configuration

Overview

Anonymous Access Configuration in CloudBeaver enables users to interact with databases without authentication. There are two methods for setting up anonymous access:

  • Administrator defined connections: Administrators can configure connections that are accessible anonymously, allowing access to these predefined connections.

  • Private connections: When enabled, this feature lets anonymous users configure their private connections from the main page. These connections are temporary and expire with the session.

By adhering to the settings below, CloudBeaver can be configured to allow anonymous access through both administrator-defined and user-customized connections.

Important: If the Allow anonymous access checkbox is not selected, the functionality for anonymous access is disabled, restricting the use of CloudBeaver to authenticated users only.

Configuration methods

Enabling private connections for anonymous users

  1. As an administrator, navigate to the Settings -> Server configuration.

  2. Locate the Enable private connections option and activate this setting to allow the creation of connections by anonymous users.

  3. Save changes.

Note: Connections created by anonymous users are not permanent. These connections will be terminated following the session expiration.

Administrator defined anonymous access

  1. Start the process of creating a connection as an administrator. For detailed instructions, refer to the Create Connection article.

  2. Navigate to the Access tab within the connection settings and click on the Edit button to modify access settings.

  3. Choose user (representing all users, including anonymous) from the list and click Add to include this user group in the access rights.

  4. Once all the connection settings are configured, click the Create button to establish the new connection.

Note: If the administrator has enabled the Enable private connections option, anonymous access cannot be configured for that specific database.

Did we resolve your issue?