On 04/23 12:25 Joel Rees wrote: > Timothy Fisher commented: > > I understand the question as he's wondering whether or > > not you could programatically authenticate a user, > > such that the container would then recognize the user > > as being authenticated and not require another login > > when viewing pages designated as protected by the > > container. > > So, do you have a container-managed solution?
Somebody does... Take a look at http://jakarta.apache.org/turbine/ Turbine would be the ultimate servlet container that will take charge in running all your other servlets, so that handling users that are authenticated or not yet authenticated becomes a piece of cake. Of course, there's a learning curve to climb, but I believe that it would be worth it. (eg: if your client entered "http://yourhost.com/some/path/to/a/plain.html" in his/her browser and yet he/she was not logged in, the request would be redirected to a login form you had designated.) Oki -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
