I have tried to do the exact thing that Jeromy suggests below with 2
packages. And then in the web.xml specify a security constraint with the
URL pattern "/protected/*". After doing so, I am not getting the result
that I think I should be.
When issuing a request for my action at
"http://localho
t;> issue [though the pace is slow].
>>
>> Also keep in mind, the same issue exists on WAS 7.0.0.1 with a slight
>> variation. If this is determined to be a Websphere problem with WAS 6.1.
>> Then I have a stronger case to press issue for WAS 7.0.
>>
>> --- On
I installed the latest fix pack for WebSphere, bringing my version up to
6.1.0.21 and it did the trick. The Web container authentication now works
as I expected it to.
Thanks for the feedback.
Pete.
pblatner wrote:
>
> I don't see how this fix applies to the problem I ment
3 matches
Mail list logo