Yes other tools manage it in a rather simple way
- sqlplus :sqlplus /@SID
- TOAD : you use an "EXTERNAL" account and leave the password field blank :
It's rather a nice feature preventing the necessity of providing password for users whose password have been stored in the wallet:
For you information you manage your wallet via a tool named "mkstore" (create, display, update, delete encrypted entries ) and you can use it by providing following lines in your standard sqlnet.ora :
<< sqlnet.ora >> :
WALLET_LOCATION =
(
SOURCE =
(METHOD = FILE)
(METHOD_DATA =
(DIRECTORY = C:\Oracle\wallet)
)
)
SQLNET.WALLET_OVERRIDE = TRUE
<< >>
In this example "C:\Oracle\wallet" is the wallet directory containing next 2 encrypted files :
- cwallet.sso
- ewallet.p1
I think Lab128 could handle it the same way that TOAD does with a special username such as EXTERNAL - leaving the pasword field empty.