Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 111 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 475 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Wallet location set in VSCode settings is ignored

Wallet location is taken from file: .\client\NETWORK\ADMIN\sqlnet.ora insead of location provided in VSCode settings.
Answers
-
Is this in a running script where you issued a CONNECT command in the script itself?
Or are you simply associating a file with a connection shown in Oracle Explorer?
Finally, can you go to the connection dialog and verify that you checked "Use Wallet File" and verify that the Wallet File Location in the connection dialog is correct?
-
I am not using created connections, but I am using CONNECT command directly in scripts.
-
Hi,
We just released version 19.3.4 which should fix this issue. Could you please try it out and let me know?
-
looks like it is still taking path from: .\client\NETWORK\ADMIN\sqlnet.ora
instead of setting parameter: changing oracledevtools.connectionConfiguration.walletFileFolder
-
Can you please provide some more details of what exactly you are doing?
For example:
1) what is your connect statement?
2) Why did you mention sqlnet.ora? Is there a path in the sqlnet.ora itself that is being ignored? If so please provide your sqlnet.ora as well.
-
In addition to my last two questions can you please also let me know:
3) Please send your settings for "Config Files Folder" and "Wallet File Folder"
4) In your "Config Files Folder" , do you have a tnsnames.ora and a sqlnet.ora ?
5) If you have a sqlnet.ora, is WALLET_LOCATION set in sqlnet.ora ?
6) The connect command you are issuing in your script (without the password)
-
I believe that oracledevtools.connectionConfiguration.walletFileFolder is to tell the extension location of the wallet. That means that based on provided path the extension should access the wallet and take passwords while wallet connection is created in VSCode ora while using directly CONNECT /@MY_DB. Please correct me if I am wrong.
My sqlnet.ora file:
Setting in VSCode:
Extension takes "C:\\Dane\\config\\wallet" from sqlnet.ora instead of "C:\\Dane\\config\\second_wallet" provided in extension.
I believe its a bug. If not the parameter oracledevtools.connectionConfiguration.walletFileFolder is useless and should be deleted.
-
Hi,
Please see my post in your other thread. I think they are possibly the same issue.
If you are connecting using:
CONNECT /@MY_DB
And your SQLNET.ORA contains:
SQLNET.AUTHENTICATION_SERVICES =(NTS)
If so, this means you are on Windows and are using OS Authentication. The password is NOT coming from the wallet. It is coming from the Windows OS. The wallet is not involved. Generally the wallet is used to secure the network connection, not for authentication of a user id (not always - there is something called "global userid" but I don't think that is the case here).
So the question becomes, did you ever get this working in the past? It may be an OS Authentication issue. If you aren't on Windows, maybe you got this SQLNET.ORA from a Windows system and it is not valid here. If so please let me know what platform you are on, and if any other tools are able to connect on that system and how they are configured.
-
Thanks for your answer in my second thread.
My answers:
- You are right, I am using Windows 10.
- My current sqlnet.ora file looks exactly like in post above
- I set
SQLNET.WALLET_OVERRIDE
to TRUE to use wallet instead of default Windows OS Authentication - I am successfully able to connect to DB using command: CONNECT /@MY_DB via:
- SQL Developer - all connection stored in wallet
- SQLcl - all connection stored in wallet
- VSCode extension - only if the wallet stores no more than 159 connections (otherwise I cannot connect to none of connection stored in wallet) - issue details here: https://community.oracle.com/tech/developers/discussion/4479585/wallet-stops-working-when-contains-more-than-159-connections#latest)
- Connections I am able to connect via wallet are placed into my wallet (by using command: mkstore -createCredential) and into tnsnames.ora file.
- I used following link to set up passwordless connection with Secure External Password Store: https://docs.oracle.com/cd/B19306_01/network.102/b14266/cnctslsh.htm#CBHGEBEI
My questions:
- If I understand correctly the oracle wallet (Secure External Password Store) works kinda like password-less ssh connection, right?
- Could you please tell me what is the following setting parameter for?:
changing oracledevtools.connectionConfiguration.walletFileFolder
-
Thanks for the detailed response! I am following up with the engineering team.
One more question: If you put the wallet in a different location can you get this to work with the vs code extension?
To (try to ) answer your question:
1) In most cases the wallet secures the connection and then users provide a database user/pass on top of that. So the dialog takes user/pass, tns location, and wallet location. But in your case you are using Secure External Password Store which seems to use the wallet to also store the password. (This is not my area of expertise so I am following up)
2) oracledevtools.connectionConfiguration.walletFileFolder is just the default folder that any connection that uses a wallet is supposed to get it from. If you specify a wallet and it is not coming from that location, but instead is coming from somewhere else, I believe that is a bug. (that we thought we had fixed in 19.3.4)