RE: Apache authentication and JSP execution

Mike,

The answer is maybe. The first thing is if you're using connection
pooling (which you should for performance reasons), you can't do this.
The connections are established by the pool manager and the user name
and password is set when the server starts up.

If you are not using connection pooling, you can specify the user name
and password for each connection. Getting the user name is easy enough
but I'm not sure how you go about getting the password to connect with.
One idea may be to have your stored procedure switch profiles before it
does any IO. If you do this, you need to make sure that you ensure that
the profile is always switched back regardless of if an error occurs and
that it always releases the profile handles (bad things can happen when
the system runs out of them).

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Cunningham
Sent: Thursday, July 07, 2005 4:06 PM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] Apache authentication and JSP execution

We have our first JSP based app going into final testing. The JSP uses
calls to stored procedures to access the database and so must make a
connection to the database and provide a userid and password. The
website being developed is setup in Apache to require OS/400 userids and
passwords. Is there any way to use the Apache authenticated userid and
password to make the connection to the database or is the only option to
create a special userid and password to be used by the JSPs ? I would
like to still be able to use journaling to record who is accessing the
database.