Hehehe thanks anyway, i appreciate it. But yes, it was the comparison and the
case of both words.
Le 27/09/2010 à 21:57, Bob Hall a écrit :
> Oops, just saw the [solved] msg...
>
> --- On Mon, 9/27/10 at 7:55 PM, Bob Hall wrote:
>
>> --- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R
>>
Oops, just saw the [solved] msg...
--- On Mon, 9/27/10 at 7:55 PM, Bob Hall wrote:
> --- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R
>
> wrote:
>
> > > The security-role is right below the
> > security-constraint
> > > closing tag and above the login-config opening
> tag.
> >
> > Sorry
Julio,
--- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R
wrote:
> > The security-role is right below the
> security-constraint
> > closing tag and above the login-config opening tag.
>
> Sorry, I missed it. However, the
> element normally comes /after/
> ; not sure if that's required by
mail.com]
>> Subject: Re: Tomcat ldap authentication with 403 Forbidden error
>
>> The security-role is right below the security-constraint
>> closing tag and above the login-config opening tag.
>
> Sorry, I missed it. However, the element normally comes
> /after
> From: Julio César Chaves Fernández [mailto:hent...@gmail.com]
> Subject: Re: Tomcat ldap authentication with 403 Forbidden error
> The security-role is right below the security-constraint
> closing tag and above the login-config opening tag.
Sorry, I missed it. However,
Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Julio César Chaves Fernández [mailto:hent...@gmail.com]
> > Subject: Tomcat ldap authentication with 403 Forbidden error
>
> > i'm working with Tomcat
>
> What *exact* version?
>
> > This is th
> From: Julio César Chaves Fernández [mailto:hent...@gmail.com]
> Subject: Tomcat ldap authentication with 403 Forbidden error
> i'm working with Tomcat
What *exact* version?
> This is the security section in the app web.xml
I don't see any element in the above, which
Hi, i'm working with Tomcat and i've configured a Realm for user
authentication against Oracle OID. Sniffing the communication between the
client and the OID server everything seems to be fine, but when the user
authenticates the application then displays the 403 forbidden error page.
This is the
