> From: DIGLLOYD INC [mailto:[EMAIL PROTECTED]
> Subject: Re: authenticated but not authorized -- blank page
>
> Is it because there is more than one name> specified eg it needs to be:
>
>
> guest1
>
>
> guest2
>
Yes, the javaee schema allows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd,
DIGLLOYD INC wrote:
| I don't read schemas well. Perhaps if you would be so kind as to
| explain why it's wrong? Is it because there is more than one
| specified eg it needs to be:
|
|
|guest1
|
|
| guest2
|
That's exactly righ
I'm using:
http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
"
version="2.5">
I don't read schemas well. Perhaps if you would be so kind as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd,
DIGLLOYD INC wrote:
|
| guest1
| guest2
|
Not sure if Tomcat actually cares, but this is an invalid configuration.
Look at the DTD or Schema (whichever one you are using) again.
- -chris
-BEGIN PGP SIGNATURE-
Version:
:
From: DIGLLOYD INC [mailto:[EMAIL PROTECTED]
Subject: authenticated but not authorized -- blank page
I have a webapp 'guest', with two subfolders 'guest1' and
'guest2'.
Really? Because that's not what's in your security constraints:
/_guest1_/*
: DIGLLOYD INC [mailto:[EMAIL PROTECTED]
Subject: authenticated but not authorized -- blank page
I have a webapp 'guest', with two subfolders 'guest1' and
'guest2'.
Really? Because that's not what's in your security constraints:
/_guest1_/*
/_guest
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: authenticated but not authorized -- blank page
>
> oh okthat's about the only difference I saw between mine
> and his...I've had no difficulty getting the appropriate
> errors I should but I thoug
lto:[EMAIL PROTECTED]
Sent: Friday, May 02, 2008 12:33 PM
To: Tomcat Users List
Subject: RE: authenticated but not authorized -- blank page
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: authenticated but not authorized -- blank page
>
> I'm on an older version
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: authenticated but not authorized -- blank page
>
> I'm on an older version of Tomcat, but I don't have a
> separate security-role atttribute tag like his:
>
>
>
> guest1
>
ubject: RE: authenticated but not authorized -- blank page
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: authenticated but not authorized -- blank page
>
> I actually have my role names defined within EACH constraint.
So does Lloyd:
>
>
>
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: authenticated but not authorized -- blank page
>
> I actually have my role names defined within EACH constraint.
So does Lloyd:
>
>
> ...
>
> From: DIGLLOYD INC [mailto:[EMAIL PROTECTED]
> Subject: authenticated but not authorized -- blank page
>
> I have a webapp 'guest', with two subfolders 'guest1' and
> 'guest2'.
Really? Because that's not what's in your security constra
I actually have my role names defined within EACH constraint.
-Original Message-
From: DIGLLOYD INC [mailto:[EMAIL PROTECTED]
Sent: Friday, May 02, 2008 10:56 AM
To: Tomcat List Users
Subject: authenticated but not authorized -- blank page
I have a webapp 'guest', with two
I have a webapp 'guest', with two subfolders 'guest1' and 'guest2'.
These are protected by security constraints.
/guest/guest1 has a security constraint requiring role 'guest1'
/guest/guest2 has a security constraint requiring role 'guest2'
Users 'guest1' and 'guest2' map to roles of the sam
14 matches
Mail list logo
