Issue

• Currently, when Jira connects to the Oracle database in the installation wizard, it only has the option of configuring hostname, port, service, username, and password.
• Because Jira doesn't have a way to point to a tnsnames.ora file or manually construct the connection string to utilize either Oracle Wallet OR the Java Keystore (JKS) methods, we are not able to use Oracle Autonomous Transaction Processing, which is very crucial to our business.

Sample from tnsnames.ora

oacipoc_tp = (description= (address=(protocol=tcps)(port=1522)(host=adb.us-ashburn-1.oraclecloud.com))(connect_data=(service_name=wijnknlzqi7jmor_oacipoc_tp.atp.oraclecloud.com))(security=(ssl_server_cert_dn=
"CN=adwc.uscom-east-1.oraclecloud.com,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US")) )

sample from ojdbc.properties:

oracle.net.wallet_location=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/u01/app/oracle/wallet)))

Suggestions

• Ideally, during the installation wizard, after you selected "oracle" as your DB type, there would be an "advanced" button, where when you clicked it, it would allow a user to input a fully formed JDBC connect string. (Or even better, an "Oracle Cloud" option which would just allow the user to select the downloaded wallet.zip file, read the file, and select the proper connect stanza)

• In addition, when the user clicked "next" on the bottom of the DB setup screen that the installer would test for a file named something like 'oracledbsetup.xml'. If the file existed, that the connect string in the file would over-ride whatever data was inputted in the DB setup dialogue and allow us to provide the connection string that way so that we would be able to use Oracle Autonomous Transaction Processing.