Hot answers tagged

3

My goal with this question was to determine how mkstore could be scripted. Here is the method I came up with using Powershell. Here are the requirements: PowerShell is installed. Scripting is enabled (Set-ExecutionPolicy RemoteSigned run as administrator). The script is in c:\oracle\WalletCreator. Wasp.dll from Windows Automation Snapin for PowerShell is ...


1

General Information about Oracle Wallet is in the Advanced Security Guide. This is the link to managing wallets from the command line using the general orapki tool. This is the link to managing wallets using the MKSTORE command specific to credentials storage. *add Here is some q&a on the steps on asktom. He also notes an Oracle bug 4395883 that can ...


1

One way to do this is to specify an Advanced Connection Type and enter a custom JDBC URL as follows: jdbc:oracle:oci:/@myDatabase In addition the "OS Authentication" check box needs to be checked. This would seem to cause it to pass the OS username and password, but apparently (perhaps because I don't have NTS set as an authentication service in my ...


1

In case anyone is interested in the solution that was identified: The sqlnet.ora in question contained the following: ENCRYPTION_WALLET_LOCATION = (SOURCE = (METHOD = FILE) (METHOD_DATA = (DIRECTORY = ${ORACLE_BASE}/admin/${ORACLE_SID}/wallet) ) ) Which worked fine with the oracle user profile on the server. However, ...


1

In some versions of Oracle, you cannot put space between the beginning-of-line and the WALLET_LOCATION keyword, and you must put space between the beginning-of-line and the definition of a wallet. Your snippet indicates that you failed at one of these things. I think they removed this silly requirement starting from some Oracle version, but better safe than ...


1

I was able to figure out from the trace file that there was line in the sqlnet.ora file that it didn't like. I narrowed it down to the WALLET_LOCATION line and finally recognized that there was a missing parenthesis at the end of the line.


1

ORA-24247 is something you would get after you already have a connection and are trying to use a network resource (such as UTL_HTTP). It sounds like you need to create an ACL (Access Control List). See http://oraclepoint.com/oralife/2010/10/08/configuring-wallet-manager-to-enable-https-connect-with-oracle-11g-database/.



Only top voted, non community-wiki answers of a minimum length are eligible