Using DB & Server Access Control Client

Prev Next

Available in VPC

The client is an agent program you install on your PC to connect to servers or databases through DB & Server Access Control. Connections through the client are relayed to the target resource through a proxy server. Connection history, executed commands, and queries are recorded in Cloud Log Analytics.

Note

You can download the client installer in the NAVER Cloud Platform console. The client supports Windows and macOS. For more on how to download it, see Proxy Server.

Client interface

The client interface includes the following components after you log in:

dsac-client_01_kr.png

Component Description
① Select language Select Korean, English, or Japanese as the client interface language.
② [Sync access control policies] Update the list by retrieving the latest access permission information from the proxy server. Since it does not update in real time, synchronization is required to reflect the latest status if permissions change.
③ Access granted list Lists targets that the logged-in sub account has permission to access.
  • [DB] tab: Lists database targets you have permission to access. Includes target name, resource type, private domain (IP address), and access port information.
  • [Server] tab: Lists server targets you have permission to access. Includes target name, private domain (IP address), and access port information.
④ Log out Log out of the client.

Log in from an internet environment

In an environment with internet access, connect to the proxy server via an SSL VPN and log in with your NAVER Cloud Platform sub account. To log in:

  1. Run the client.
  2. On the Connection environment settings page, select Internet.
  3. Click [Log in].
  4. When the sub account login popup appears, enter your sub account ID and password to log in.
  5. After you log in successfully, the list of database and server targets you have permission to access appears.
Note
  • You cannot log in to the client with your main account. Be sure to log in using a sub account.
  • If access permissions for DB & Server Access Control Target are not set for the sub account, the Target list will not be displayed after logging in. Check the user-defined policies for the relevant sub user in Sub Account.

Log in from a closed network environment

In a closed network environment where internet access is blocked, connect to the proxy server via an IPsec VPN and log in using your sub account's Access Key, Secret Key, and OTP. To log in:

  1. Run the client.
  2. On the Connection environment settings page, select [Closed network].
  3. Enter the IP address of the closed network proxy server you want to access and click [OK].
  4. On the login page, enter the following information:
    • Access Key ID: The access key of the sub account you want to log in with.
    • Secret Key: The secret key of the sub account you want to log in with.
    • OTP Serial Number: The OTP serial number registered to the sub user.
  5. Click [Log in].
  6. After you log in successfully, the list of database and server targets you have permission to access appears.
Note
  • You can check your Access Key ID and Secret Key on the NAVER Cloud Platform console by navigating to My Page > Account management > Authentication key management, or in the sub account details section of the Sub Account service.
  • The OTP serial number is the serial number issued when registering an OTP to a sub account. An OTP must be registered on the sub account in advance.

Log out

To log out of the client:

  1. Run the client.
  2. Click [Log out].
  3. When the popup appears, click [Yes].
    • After you log out, the login page appears.

Sync policies

If sub account permissions change, you can synchronize to reflect the latest access permission information in the client. The client's target list displays information from the time of login and is not updated in real time. To sync policies:

  1. Log in to the client.
  2. Click [Sync access control policies].
    • The DB and server target lists are updated by retrieving the latest access permission information from the proxy server.