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
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> So it seems to me that it is not correct for the realm name
> to be overriden by the error page.
Actually, I think it is. The reason the is cosmetic in the
case
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 somet
>>
>> 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
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> But why does my custom app display "JDBCRealm" in the credentials
> prompt?
Because the 401.jsp file in the manager webapp overrides the default
dial
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
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> Implementing a JAASRealm sounds easy enough
I wasn't suggesting that you convert to a JAASRealm, but just providing
evidence that the manager webapp i
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
> From: Caldarale, Charles R
> Subject: RE: Manager app authentication not working with JDBCRealm
>
> Note that we left the for
> org.apache.catalina.UserDatabase alone.
Also, we did not change the under in the
manager web.xml file, although I don't think that wi
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> 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,
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
Mark Leone wrote:
Tomcat 6 still has the html page for the admin app that
says it can be downloaded if desired, so I assumed it was still
supported for 6.0.
This should be fixed (ie removed) by the next release.
Mark
-
To st
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> 2. I added to server.xml the JDBCRealm descriptor that I
> showed earlier in the thread. I made no other changes.
O.k., I think that will break the world. A
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
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> Mar 19, 2008 10:21:23 PM org.apache.catalina.startup.HostConfig
> checkResources
> INFO: Undeploying context [/admin]
There is no admin webapp for Tomcat 6
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'
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Re: Manager app authentication not working with JDBCRealm
>
> I'm using Tomcat 6.0.16. I have my JDBC Connector jar
> file in %catalina_home%\lib
O.k., that looks good.
Why do your posted XML fragments have asterisks
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.
> From: Mark Leone [mailto:[EMAIL PROTECTED]
> Subject: Manager app authentication not working with JDBCRealm
>
> 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
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
20 matches
Mail list logo
