Advertisement

01.21.2008 at 02:30PM PST, ID: 23099606
[x]
Attachment Details

Configuring Oracle wallet using mkstore for genuine external connections

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.6
Tags:

Oracle, Oracle client, 10.2.0.3, Secure External Password Store configuration

I can succesfully use the Oracle 10 mkstore utility to create credentials to allow external-style connections (i.e. /@instance) to databases with internal users. This involves adding a couple of wallet-enabling lines to TNS_ADMIN/sqlnet.ora, as per http://download-uk.oracle.com/docs/cd/B19306_01/network.102/b14266/cnctslsh.htm. So far so good.

I can also, by reverting TNS_ADMIN, connect as a good old-fashioned external user to another database.

However, my app needs to connect to both at the same time, i.e. within the same environment. This fails, i.e. if TNS_ADMIN is wallet-enabled, the genuine external connection fails with "invalid username/password; login denied" message. If TNS_ADMIN is not wallet-enabled, the internal connection cannot connect as /@instance, obviously.

Is there a solution to allow persistent connections to both within the same application/environment? Some undocumented tweak to mkstore syntax possibly to allow 'pseudo' credentials to be stored for genuine external users, so wallet can be used for both? Or other solution?

Many thanks in advance.
Answered By: brodney
Expert Since: 09/14/2004
Accepted Solutions: 1
brodney has been an Expert for 4 years 3 months, during which he has posted 7 comments and answered 1 question. brodney is just one of 761 experts in the Oracle 10.x Zone. 2 experts collaborated on this answer, which was graded an "A" by the asker.
 
 
 
 
20081119-EE-VQP-48 / EE_QW_2_20070628