8.3 Configuring the Centralized Configuration Provider Naming Method

With this naming method, connect identifiers are mapped to connect descriptors contained in a Centralized Configuration Provider, such as Azure App Configuration store or Oracle Cloud Infrastructure (OCI) Object Storage as a JSON file.

Optionally, you can also store database credentials (such as database user name and database password) and Oracle Call Interface attributes (such as statement_cache_size, prefetch_rows, or session_pool) in a Centralized Configuration Provider. You need to use Azure Key Vault or OCI Vault to store the database password, and then add a reference to that vault in your Centralized Configuration Provider. You can also store an Oracle wallet in Azure Key Vault or OCI Vault, and then add a reference to that vault in your Centralized Configuration Provider.

A connect identifier here includes instance-specific details of a Centralized Configuration Provider (such as server name or app configuration name), path, and authentication details. Database clients can securely look up the configuration data from your Centralized Configuration Provider and connect to the database.

Note:

In addition to the Azure App Configuration store and OCI Object Storage, JDBC supports built-in Centralized Configuration Providers such as HTTPS provider and File provider (see Oracle Database JDBC Developer’s Guide). Also, ODP.NET supports local file system access for web and desktop apps (see Oracle Data Provider for .NET Developer's Guide).

Use one of the following Centralized Configuration Providers:

• Azure App Configuration Store
  Stores configuration data in the Azure App Configuration store as key-value pairs, which are accessible with network service name paths as URI.
• OCI Object Storage JSON File
  Stores configuration data in the Oracle Cloud Infrastructure (OCI) Object Storage as a JSON file.