- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
05-13-2025 09:01 AM
I'm trying to get the new Oracle SQL Developer ConnectionComponent (v20.0) to work on a Privilege Cloud environment.
I've set the java directory via both the jdk.conf and sqldeveloper.conf files (although I suspect only the 2nd was required), I have configured the "Use Oracle Client" and TNSnames.ora file in the SQL-Developer preferences, and edited the correct tnsnames.ora in the InstantClient path.
Yet, somehow the sessions are not connecting. The client loads on instantiating a session, but the "Select Connection" dialog box appears behind the "Connecting" scroll-bar, yet a connection is never selected (I am assuming this connection selection is a drop-list fed by the tnsname.ora file).
The documentation alludes to a TNSSERVICENAME as a file category?
https://docs.cyberark.com/privilege-cloud-shared-services/latest/en/content/pasimp/psm_oracle_sql.htm?Highlight=PSM%20Oracle%20SQL%20Developer#Defineaccountsettings
Or the CPM component seems to allude to it as a portion of the ConnectionString?
https://docs.cyberark.com/privilege-cloud-shared-services/latest/en/content/pasimp/odbcplugin.htm#Addthepassword
Anyone have an idea on what I am missing?
05-13-2025 09:15 AM
For additional context, after the "Select Connection" times out, the normal connection dialog loads in concurrency to a PSM "Session has been closed" error. This screen also fails to receive any connection data and does not attempt to establish a DB connection.
05-13-2025 03:51 PM
Hi @Michael Bagley
Have you allowed AppLocker policies on the PSM server include the execution of SQL Developer and its associated Java components?
Also please refer to the following community thread.
Hope it helps !
05-14-2025 05:04 AM
Currently AppLocker is in "Audit" only mode while I test and get the ConnectionComponent working. So I am positive AppLocker is not the issue.
I will try the edits to the sqldeveloper.conf file as suggested in the topic you linked to, and see if any of those help.
05-22-2025 12:22 AM
Hello @Michael Bagley
Have you received an answer to your question? If so, we kindly encourage you to share it with us.
Your insights could be valuable to other community members in the future.
Thank you, Isar.
06-02-2025 11:16 AM
The issue was that the database users did not have certificates tied to their Oracle DB accounts, and Oracle SQL Developer v20+ mandates this for the default authentication methods. While a human use can select the options in the interface to not require a certificate, the automation has been designed to use the defaults and hence must meet this mandate.
The only way around this would be to create an AutoIT based custom connection component that has the logic to leverage the non-certificate based authentication methods rather than the default.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

