Re: User authentication

If I understand the problem correctly I believe 3.0 does both. If you don't save the user ID and password in the DAD then the server will prompt you for your Oracle user ID and password when you access an application (PL/SQL app). If you do supply an ID and password you can still protect the application using a userid/password pair held on the OWS. There is a section in the manual about it. I've tried both and it seems to work ok.

Steven Rorabaugh wrote:

> Our system administrators are in the process of upgrading from Oracle web server 2.1 to 3.0 . Web server 2.1 uses "user authentication", i.e, a predefined set of user_id/password pairs to authorize access to a particular web application. A separate single Oracle user/password is used to gain access to the Oracle
> database involved. Web server 3.0 uses "database authentication" to authorize
> access to the application. That is, a user of the application "authenticates"
> himself by entering a valid Oracle user_id/password pair. No pre-defined
> Oracle user is associated with the connection to the Oracle database.
>
> We would like to move to web server 3.0, but for reasons pertinent to the
> application, would like to retain the "user authentication" scheme incorporated
> in web server 2.1 . Our system administrator tells me that "user
> authentication" is not supported under 3.0 . I think he's wrong, but cannot
> find any specifics in the literature available to me to prove my point. Is he
> correct? If not, how can I prove it?
Received on Thu Mar 11 1999 - 07:56:28 CST