RE: RE: Authenticate web users against Validation Lists

This is a very common approach. Our organization uses Mainsaver
(maintenance/crib inventory package) with an AS/400 backend database, and
ADP HRizon/EV2 (MS SQL/Oracle backend). In both cases, the application front
ends (web page or client server) utilize "user logins". However, all
back-end requests go through a single database user.

Loyd

-----Original Message-----
From: Joel R. Cochran [mailto:jrc@masi-brac.com]
Sent: Thursday, January 31, 2002 12:01 PM
To: 'web400@midrange.com'
Subject: RE: [WEB400] RE: Authenticate web users against Validation
Lists


This is kind of stream of thought, so bear with me...

You could setup a properties file with a generic userid and password, then
set up a corresponding userid/password on the 400 that is restricted to the
areas you want this Java application to access.  Use JPassword fields in an
Applet to receive the user's information.  Verify in your servlet that the
user's information is formatted correctly (you'll ahve to come up with your
own approach), and if it is valid then use the sign-on info from the
properties file for your JDBC connection.

This way you can limit 400 access to a single userid/password but still give
each user a unique sign on and none of them know the actual AS/400 sign in
information.

Joel R. Cochran
Director of Internet Services
VamaNet.com
(800)480-8810
mailto:custservice@vamanet.com