FWIW our apps all store them (encrypted) in the registry - this obviously
goes for windows only. for web apps wrox press have a nice approach which is
to store connection strings in a shared library where they are accessible as
public properties. I guess you could do this with a client app as well.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Nathan Hodgen" <nathan_hodgen_at_yahoo.com> wrote in message
news:8e9777d1.0204030528.3b0380c7_at_posting.google.com...
> Thanks Daniel,
>
> I am sorry. When I said client, I did not mean an Oracle client. I
> meant any general client like a COM object or an ADO connection.
>
> The users I have supported in the past have either hardcoded the login
> credentials in their code or stored them in the registry (speaking of
> a windows environment). Is there a better way to do this?
>
> Thanks again,
> Nathan
>
> damorgan <damorgan_at_exesolutions.com> wrote in message
news:<3CA9D663.45F5BDE2_at_exesolutions.com>...
> > Typically in an Oracle application one never stores them.
> >
> > Which part of the Oracle security model doesn't work for you.
> >
> > Daniel Morgan
> >
> >
> >
> > Nathan Hodgen wrote:
> >
> > > What is the standard place, if there is one, for storing username and
> > > password for an Oracle account in a client? Traditionally (in a
> > > windows 2k envirnoment), I have stored the connect string encrytped in
> > > the registry.
> > >
> > > THANKS,
> > > Nathan
Received on Wed Apr 03 2002 - 08:15:36 CST
