I've been running Tomcat since version 4. Today, running 7.0.12, I
decided to define a non-standard context, and I can't get it to work
after carefully following all the instructions in the documentation and
doing what all my searching confirmed I should be doing.
My web app is deployed at $C
Caldarale, Charles R wrote:
Since there doesn't seem to be any means of the 401.jsp to interact with
the declared to determine or specify the other necessary
attributes for a digest 401 response (e.g., the nonce), it looks like
it's impossible at this time to use a custom 401 handler with
cont
Mark Leone wrote:
Perhaps since I used DIGEST authentication, it was necessary to put the proper name
of the realm in , despite what you said above. I know I had in this
element at first the same realm name I used for generating the digested password in
my datastore; but perhaps I had
>>
>> But why does my custom app display "JDBCRealm" in the credentials
>> prompt?
>
>Because the 401.jsp file in the manager webapp overrides the default
>dialog box; since your custom webapp has no such error page, the
> is used. Note that is purely cosmetic; you
>can put anything you want t
I noticed that the prompt for my credentials says
"Enter username and password for 'Tomcat Manager
Application'".
That prompt comes from the 401.jsp file in the manager webapp, not the
in the web.xml file; I don't think the is
actually used anywhere.
But why does my custom app disp
Caldarale, Charles R wrote:
I wonder if the use of the UserDatabase resource is
hard-wired into the manager app somehow.
It's not; we use a JAASRealm for Tomcat 6.0.16 production, and the
manager app quite happily authenticates with that. All we changed in
server.xml and the manager's we
O.k., I think that will break the world. As far as I know, you may have
only one inside a given container (, , );
a at a lower level overrides any at a higher one. If you want
all apps to use your JDBCRealm, you have to remove (or comment out) the
default one for the .
I commented out t
There is no admin webapp for Tomcat 6; is that your own, or did you copy
over stuff from a previous level of Tomcat? If you did, that's likely
the cause of your problem, since the configs and built-in webapps are
not compatible across levels.
I copied the admin app from Tomcat 5 after seeing
Why do your posted XML fragments have asterisks and odd annotations like
<#>? Since what you posted doesn't appear to be just a copy & paste, it
would be good to see the actual elements, attributes, and values.
My mistake. I copied from the rendered XML doc instead of from the
source. Here'
I wonder how many times we have to remind people to provide the Tomcat
level they're using.
Besides that rather critical piece of information, also tell us where
you put your driver classes or jar for accessing the authentication
database.
- Chuck
Sorry about that. I'm using Tomcat 6.0.16.
I can't get the manager app working with authentication using JDBCRealm,
even though I've configured it identically to an app I developed that
uses the same JDBCRealm instance successfully. In both cases, the app
requires a user with role "manager", and the same authentication setup
works for m
Found the problem. The docBase path was wrong. The "server" node in the
file tree was a hangover from Tomcat 5.
Mark Leone wrote:
Is RemoteAddrValve broken in 6.0.16? I have the following in
"manager.xml", located at %catalina_home%\Conf\Catalina\Localhost
Is RemoteAddrValve broken in 6.0.16? I have the following in
"manager.xml", located at %catalina_home%\Conf\Catalina\Localhost.
allow="127\.0\.0\.\d"/>
I also tried allow="^127\.0\.0\.\d", but I saw a bug fix for 6.0.12 that
said it would work the way I have it in the first example.
Wh
Mark Leone wrote:
I have tomcat 5.5.17 and I recently downloaded the admin web app. I
can't seem to find a way to authenticate to it. I have an existing
JDBCRealm that works fine with the manager web app, using digested
passwords. I added a user with a non-digested password, since admin
I have tomcat 5.5.17 and I recently downloaded the admin web app. I
can't seem to find a way to authenticate to it. I have an existing
JDBCRealm that works fine with the manager web app, using digested
passwords. I added a user with a non-digested password, since admin uses
FORM authentication,
15 matches
Mail list logo
