Using an LDAP Connection to an Oracle Database

Use this type of connection to use a service definition stored on the LDAP server for server for the connection information to use. The connection information is substituted in parameters in the JDBC driver when the connection is attempted. 

Supported LDAP Services

Oracle Internet Directory (OID) is the LDAP service supported. 

Datical DB Liquibase Enterprise supports simple bind authentication through LDAP using an anonymous (empty) bind DN. 

Constraints on

...

Liquibase Enterprise Features for Oracle

...

...

You cannot use the Datical Accelerator for Oracle in projects or DbDefs where you are using an LDAP connection.. 

See Datical Accelerator for Oracle. 

Prerequisite: LDAP Server Access

These instructions assume that you have done the following:

• The Datical DB The Liquibase Enterprise host can access the LDAP server through the network. 
• You have access to the LDAP server and can create service definitions there. 

...

In the following example, the service definition on the LDAP server is named ORA_AWS_LDAP. You may name it as you wish. Use this name for the TNS Alias setting in Datical DB in Liquibase Enterprise projects. 

cn=ORA_AWS_LDAP,cn=OracleContext,dc=us,dc=oracle,dc=com
objectclass=top
objectclass=orclNetService
cn=ORA_AWS_LDAP
orclnetdescstring=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCPS)(HOST=aws-db1-rhel6.datical.net)(PORT=2484)))(CONNECT_DATA=(SERVICE_NAME=pdborcl.datical.net)))

...

Create a directory on the host where you run Datical DB run Liquibase Enterprise to use for the wallet file and Oracle configuration files. 

The example places it in the oracle_ldap directory under the <project> directory in the default location for Datical DB for Liquibase Enterprise projects.  If Oracle is installed on the host, another common location might be $ORACLE_HOME/network/admin.  

...

Edit the file so that LDAP is the only configuration method. first connection method listed.  Be sure to include all of the connection types that are valid in your environment, and to order them in your order of preference for connection types.  Only exclude the connection types that aren't appropriate in your environment. 

For example:  If you prefer connections to be LDAP, but if there is an issue with LDAP should try TNSNAMES, and if TNSNAMES also doesn't work then fall back to EZCONNECT, it would look like this:

NAMES.DIRECTORY_PATH=(LDAP,TNSNAMES,EZCONNECT)

ldap.ora

Configuration file that identifies the server, server type, and context to use in the connection. 

...

DEFAULT_ADMIN_CONTEXT = “ou"ou=oracledatabases,dc=mycompany,dc=com”com"
DIRECTORY_SERVERS = (ldap_server1.mycompany.com:3060:3131, ldap_server2.mycompany.com:389:636, ...)
DIRECTORY_SERVER_TYPE = OID

...

When attempting a connection, Datical DB  Liquibase Enterprise uses environment variables to find the configuration files, then gets information it needs from them. 

...

You have some flexibility in the environment variable to use. Datical DB  Liquibase Enterprise searches in the following order:  

...

Set LDAP_ADMIN to the location of the ldap.ora file. You may use another variable. 

Datical DB searches Liquibase Enterprise searches in the following order:

1. LDAP_ADMIN
2. TNS_ADMIN
3. ORACLE_HOME/network/ldap/admin

4. Set Up

...

Liquibase Enterprise Project DbDefs to Use the LDAP Connection

When you create a DbDef in a project and choose Oracle as the database type, you set the following property:

...

See also Configuring Step Settings (DbDefs)#OracleDatabaseStepSettings. 

5. Testing the Connection

See Testing Oracle Connections