locking myself in is no problem; this is an app running on a collegue's (peter antman @ jboss) heavily patched version of a JBoss 2.something loaded with tomcat and jboss dependencies.
do you know the internals of the accessinterceptor/authentification process in tomcat? Craig R. McClanahan wrote: > >On Fri, 10 May 2002, Mats Nyberg wrote: > >>Date: Fri, 10 May 2002 12:03:07 +0200 >>From: Mats Nyberg <[EMAIL PROTECTED]> >>Reply-To: Tomcat Users List <[EMAIL PROTECTED]> >>To: [EMAIL PROTECTED] >>Subject: automatic login >> >>friends, cohorts; >>have an application involving user registration and "declarative >>authorization". >>in the end of an user registration i want the newly created user also to >>be logged in >>without providing a "now you can use your new id and password to log >>in"-screen. >> >>HOWTO? >> >>i vanely thought something like -snip- would do and now after some days >>in the mud i thought >>i'd swallow my pride and ask; how do one do this? >> > >There is no portable mechanism in the current servlet API to do this for >container-managed security. You will have to either modify your copy of >Tomcat (and therefore be locked in), or use application-managed security >instead. > >>regards >> > >Craig > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
