Oracle

Last modified on August 23, 2022

Overview

A datasource consists of a database resource and the credentials used to access it. This guide describes how a strongDM administrator can add an Oracle database as a datasource in the Admin UI.

Oracle Database versions 11g, 12c, and 19c are supported for use with strongDM. For advanced users and database administrators, we primarily support versions 11 and 12 of the authentication protocol while providing partial support for version 8. Version 10 of the authentication protocol is not supported.

After completing this setup, users can follow the steps in the Oracle User Guide to connect to and use your Oracle database.

Prerequisites

To add a datasource in the strongDM Admin UI, note the following prerequisites:

  • Properly configure an account for your database resource. If you choose to store the resource credentials with strongDM, have those credentials ready. When not using strongDM, set up a Secret Store integration and be able to enter the location of the secrets required to access the resource.
  • The hostname or endpoint you enter for your resource must be accessible by at least one gateway or relay. To verify this, log in to the gateway or relay and use the nc -zv <YOUR_HOSTNAME> <YOUR_PORT> Netcat command. For example, use nc -zv testdb-01.fancy.org 5432. If your gateway server can connect to this hostname, you can proceed.

Add a Datasource

To add your new Oracle database as a strongDM datasource, use the following steps.

  1. Log in to the Admin UI.

  2. Go to Infrastructure > Datasources.

  3. Click Add datasource.

  4. Select Oracle as the Datasource Type and set other configuration properties for your new database resource.

    Add Oracle Datasource
    Add Oracle Datasource
  5. Complete all required fields.

  6. Click create to save the resource.

  7. Click the resource name to view status, diagnostic information, and setting details.

Resource properties

Configuration properties are visible when you add a datasource or when you click to view its settings. The following table describes the settings available for your Oracle database.

PropertyRequirementDescription
Display NameRequiredMeaningful name to display the resource throughout strongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource TypeRequiredSelect Oracle
HostnameRequiredHostname for your Oracle database resource; must be accessible to a gateway or relay
PortRequiredPort to use when connecting to your Oracle database; default port value is 1521
Port Override:OptionalAutomatically generated with a value between 1024-59999 as long as that port is not used by another resource; preferred port can be modified later under Settings > Port Overrides
DatabaseRequiredDatabase name you would like to connect to using this datasource
Secret Store:RequiredCredential store location with the default set to strongDM; learn more about Secret Store options
UsernameRequiredUsername to utilize when connecting to this datasource; displays when Secret Store integration is not configured for your organization or when strongDM serves as the Secret Store type
PasswordRequiredPassword for the user connecting to this datasource; displays when Secret Store integration is not configured for your organization or when strongDM serves as the Secret Store type
Username (path)RequiredPath to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-strongDM Secret Store type
Password (path)RequiredPath to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-strongDM Secret Store type
TLS RequiredOptionalIndicator to require strongDM to use TLS to connect to the database
Resource TagsOptionalDatasource tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)

Secret Store options

By default, datasource credentials are stored in strongDM. However, these credentials can also be saved in AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, or HashiCorp Vault.

Non-strongDM options appear in the Secret Store dropdown if they are created under Network > Secret Stores. When you select another Secret Store type, its unique properties display. For more details, see Configure Secret Store Integrations.

Resource status

After a resource is created, the Admin UI displays that resource as unhealthy until the health checks run successfully. When the resource is ready, the Health icon indicates a positive, green status.

Datasource Ready
Datasource Ready

When the resource does not display a positive status, click the resource name to go to the Diagnostics tab and check for errors.

If any errors occur, please copy them into an email and send it to support@strongdm.com.

Top