Oracle

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. After completing this setup, users can follow the steps in the https://app.gitbook.com/s/HaY8OFbXUreWEF61MhKm/connect/oracle to connect to your Oracle database.

Client and Version Support

StrongDM broadly supports a variety of clients for use with Oracle databases. Our automated tests check the following tools against Oracle 19c and 21c servers configured without legacy authentication modes before version 12.

Java Database Connectivity (JDBC) tools

Most of the following tools are Java-based apps and cross-platform tools that use the JDBC API for database access. They tend to use the JDBC Thin Driver (ojdbcX.jar) with no Oracle Client required.

Tool	Versions Supported With Oracle 19c, 21c	NNE Support
Thin Driver	JDBC Versions with JDK 17 23.6.0.24.10 - 23.8.0.25.04 JDBC Versions with JDK 11 21.1.0.0 23.2.0.0 - 23.8.0.25.04 JDBC Versions with JDK 10 19.3.0.0, 19.16.0.0 JDBC Versions with JDK 8 12.2.0.1 18.3.0.0, 18.15.0.0 19.3.0.0 21.1.0.0, 21.7.0.0 23.2.0.0 - 23.8.0.25.04	Yes
DBeaver	JDBC Versions with JDK 11 21.1.0.0 23.2.0.0 - 23.8.0.25.04	Yes
SQL Developer	SQL Developer 23.1.1 with JDK 11 SQL Developer 24.3.1 with JDK 17	Yes

Oracle Call Interface (OCI) tools

The below tools use OCI, a native C API provided by Oracle. These tools are often OS-specific, and are typically used by Database Administrators (DBAs) or power users. They require the Oracle Client (Instant or Full) to be installed, which provides the OCI libraries used by the tools.

Tool	Versions Supported With Oracle 19c, 21c	NNE Support
SQL Plus	Windows 21.18.0.0.0 23.8.0.25.04 macOS 19.8.0.0.0 19.16.0.0.0 23.3.0.23.09 Linux 19.27.0.0.0 21.18 23.7.0.25.01 23.8.0.25.04	Yes
TOAD	2025 R1 macOS and Windows 2025 R2 macOS and Windows	No

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.

Netcat is a network analysis tool for checking various hostnames and ports by either sending data (a ping) or checking for listeners on ports. The command in the aforementioned example uses the -z flag to check for listeners without sending data and the -v flag to show verbose output. If you do not have Netcat, you can use a package manager such as APT (Advanced Package Tool) to install it. On Linux-based distributions, run apt-get install netcat.

Add a Datasource

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

1. Log in to the StrongDM Admin UI.

2. Go to Resources > Datasources.

3. Click Add datasource.

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

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.

Oracle

Property	Requirement	Description
Display Name	Required	Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource Type	Required	Select Oracle
Proxy Cluster	Required	Defaults to "None (use gateways)"; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource
Hostname	Required	Hostname for your Oracle database resource; must be accessible to a gateway or relay
Port	Required	Port to use when connecting to your Oracle database; default port value is 1521
Connectivity Mode	Required	Select either Virtual Networking Mode, which lets users connect to the resource with a software-defined, IP-based network; or Loopback Mode, which allows users to connect to the resource using the local loopback adapter in their operating system; this field is shown if Virtual Networking Mode enabled for your organization
IP Address	Optional	If Virtual Networking Mode is the selected connectivity mode, an IP address value in the configured Virtual Networking Mode subnet in the organization network settings; if Loopback Mode is the selected connectivity mode, an IP address value in the configured Loopback IP range in the organization network settings (by default, 127.0.0.1); if not specified, an available IP address in the configured IP address space for the selected connectivity mode will be automatically assigned; this field is shown if Virtual Networking Mode and/or multi-loopback mode is enabled for your organization
Port Override	Optional	If Virtual Networking Mode is the selected connectivity mode, a port value between 1 and 65535 that is not already in use by another resource with the same IP address; if Loopback Mode is the selected connectivity mode, a port value between 1024 to 64999 that is not already in use by another resource with the same IP address; when left empty with Virtual Networking Mode, the system assigns the default port to this resource; when left empty for Loopback Mode, an available port that is not already in use by another resource is assigned; preferred port also can be modified later from the Port Overrides settings
DNS	Optional	If Virtual Networking Mode is the selected connectivity mode, a unique hostname alias for this resource; when set, causes the desktop app to display this resource's human-readable DNS name (for example, k8s.my-organization-name) instead of the bind address that includes IP address and port (for example, 100.64.100.100:5432)
Database	Required	Database name you would like to connect to using this datasource
Secret Store	Optional	Credential store location with the default set to Strong Vault; learn more about Secret Store options
Username	Required	Username 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
Password	Required	Password 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)	Required	Path 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)	Required	Path 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 Required	Optional	Indicator to require StrongDM to use TLS to connect to the database
Resource Tags	Optional	Datasource Tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)

Oracle (NNE)

Property	Requirement	Description
Display Name	Required	Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource Type	Required	Select Oracle (NNE)
Proxy Cluster	Required	Defaults to "None (use gateways)"; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource
Hostname	Required	Hostname for your Oracle database resource; must be accessible to a gateway or relay
Port	Required	Port to use when connecting to your Oracle database; default port value is 1521
Connectivity Mode	Required	Select either Virtual Networking Mode, which lets users connect to the resource with a software-defined, IP-based network; or Loopback Mode, which allows users to connect to the resource using the local loopback adapter in their operating system; this field is shown if Virtual Networking Mode and/or multi-loopback mode is enabled for your organization
IP Address	Optional	If Virtual Networking Mode is the selected connectivity mode, an IP address value in the configured Virtual Networking Mode subnet in the organization network settings; if Loopback Mode is the selected connectivity mode, an IP address value in the configured Loopback IP range in the organization network settings (by default, 127.0.0.1); if not specified, an available IP address in the configured IP address space for the selected connectivity mode will be automatically assigned; this field is shown if Virtual Networking Mode and/or multi-loopback mode is enabled for your organization
Port Override	Optional	If Virtual Networking Mode is the selected connectivity mode, a port value between 1 and 65535 that is not already in use by another resource with the same IP address; if Loopback Mode is the selected connectivity mode, a port value between 1024 to 64999 that is not already in use by another resource with the same IP address; when left empty with Virtual Networking Mode, the system assigns the default port to this resource; when left empty for Loopback Mode, an available port that is not already in use by another resource is assigned; preferred port also can be modified later from the Port Overrides settings
DNS	Optional	If Virtual Networking Mode is the selected connectivity mode, a unique hostname alias for this resource; when set, causes the desktop app to display this resource's human-readable DNS name (for example, k8s.my-organization-name) instead of the bind address that includes IP address and port (for example, 100.64.100.100:5432)
Service Name	Required	Name of the service (for example, ORCL) to connect to using this datasource
Secret Store	Optional	Credential store location with the default set to Strong Vault; learn more about Secret Store options
Username	Required	Username 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
Password	Required	Password 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)	Required	Path 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)	Required	Path 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
Resource Tags	Optional	Datasource 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 a secrets management tool.

Non-StrongDM options appear in the Secret Store dropdown if they are created under Settings > Secrets Management. 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.

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

Oracle NNE

For the Oracle (NNE) resource type, StrongDM supports the following encryption algorithms, checksum algorithims, and Oracle DB versions. Specific configuration options are presented in the Resource Properties section under the Oracle (NNE) tab. Other than those configuration options and the notes in this section about supported encryption and checksum algorithms, configuration and usage is the same for Oracle (NNE) as for the Oracle resource type.

Supported encryption algorithms

• AES-128

• AES-192

• AES-256

• DES

• RC4_40

• RC4_128

• RC4_256

Supported checksum algorithms

• SHA-256

• SHA-384

• SHA-512