Re: Struts and Websphere security - best practice

2004-08-11 Thread Ruth, Brice
Craig McClanahan wrote: On Tue, 10 Aug 2004 09:15:49 -0400, Tom McCobb <[EMAIL PROTECTED]> wrote: One thing to double check is that your welcome page really does do a *redirect* to sessionStart.do, rather than a . The latter will not kick in the container managed security, because they are

Re: Struts and Websphere security - best practice

2004-08-10 Thread Craig McClanahan
On Tue, 10 Aug 2004 09:15:49 -0400, Tom McCobb <[EMAIL PROTECTED]> wrote: > > > >One thing to double check is that your welcome page really does do a > >*redirect* to sessionStart.do, rather than a . The > >latter will not kick in the container managed security, because they > >are only applied

RE: Struts and Websphere security - best practice

2004-08-10 Thread Tom McCobb
>One thing to double check is that your welcome page really does do a >*redirect* to sessionStart.do, rather than a . The >latter will not kick in the container managed security, because they >are only applied on the URL that is originally requested from the >client (which will be the one for th

Re: Struts and Websphere security - best practice

2004-08-09 Thread Craig McClanahan
On Mon, 9 Aug 2004 10:35:14 -0400, Tom McCobb <[EMAIL PROTECTED]> wrote: > I have a struts app that I am deploying in WebSphere 5.1. Everything works > fine, no issues with WAS per se. Now I am trying to activate security and I > am running into some bumps in the road. > > The security setup is

Struts and Websphere security - best practice

2004-08-09 Thread Tom McCobb
I have a struts app that I am deploying in WebSphere 5.1. Everything works fine, no issues with WAS per se. Now I am trying to activate security and I am running into some bumps in the road. The security setup is simple: With global security enabled on WAS, authenticating against ldap (openldap