Hello
have you found any solution for this problem, because we are facing exactly
with the same problem?
For every user with small group membership the redirector works fine but for
heavy users not. We got http 413 in IIS log. If we use Jakarta 2.x then we
step a little bit further because we go
TECTED]
> To: users@tomcat.apache.org
> Subject: Re: Tomcat6+ISAPI+IIS+Integrated Authentication+Large User
>
>
> Hi
>
> I've uploaded a fresh log which shows only an attempted connection from an
> affected user (DOMAIN\mbn)
>
> A subsequent test with a '
Hi
I've uploaded a fresh log which shows only an attempted connection from an
affected user (DOMAIN\mbn)
A subsequent test with a 'normal' user produced a large log showing the
successful connection.
Thanks
Paul
Rainer Jung-3 wrote:
>
> Scrumpy Jack schrieb:
>> Hi
>> I'm trying to resolve an
Hi
Unfortunately the log I've uploaded isn't quite what you asked for. We have
little access or control over the remote system, so this is just the start
of the log. There are too many accesses in between to isolate the point
where the failing user tries to connect - other than to say it doesn't
Scrumpy Jack schrieb:
> Hi
> I'm trying to resolve an issue with Integrated Authentication when a user
> with a large Group Membership tries to access a site served by Tomcat via
> IIS ISAPI Redirect.
>
> For all other users, access is fine. For users with 70+ Windows groups, they
> are failing to
Hi
I'm trying to resolve an issue with Integrated Authentication when a user
with a large Group Membership tries to access a site served by Tomcat via
IIS ISAPI Redirect.
For all other users, access is fine. For users with 70+ Windows groups, they
are failing to be redirected and are getting a 50
