Mark Harrison schreef:
> We have a configuration file for our application that describes
> various parameters, including server configuration information.
>
> DB_CONNECT_STRING = myname/mypassword_at_myinstance
>
> I would like to not include the password in the configuration
> file, but also do not want to have users have to manually
> enter a password. (most users are unaware there is a
> database involved).
>
> This application is read-only, and is wholly contained
> within our internal network.
>
> One option I was considering was specifying the connect string
> something like
>
> myname/@myinstance
>
> and having my application fill in the password.
>
> Comments and Suggestions appreciated!
>
> Many TIA,
> Mark
Go all the way: externally identified users with certificates
to hold the user information!
Single Sign On, Oracle Certificate Authority, secured TCP - it's
all there. And I've been struggling to get it to work, but it does!
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Received on Tue Jan 23 2007 - 13:03:20 CST
