https://issues.apache.org/bugzilla/show_bug.cgi?id=55798
BJ Chippindale <bjc...@computer.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://tomcat.apache.org/to
| |mcat-7.0-doc/manager-howto.
| |html#Configuring_Manager_Ap
| |plication_Access
--- Comment #1 from BJ Chippindale <bjc...@computer.org> ---
Using Ubuntu 12.04 and Sun Java (so installed Java and Tomcat by hand) - this
was required because another app requires the Sun Java. Did NOT do this with
the default Ubuntu installer.
Tomcat is installed in /usr/local/apache-tomcat-7.0.47 Java is the latest from
Oracle-Sun.
The following is the problem.
1. In server.xml the
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
- had to be changed to -
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="/usr/local/apache-tomcat-7.0.47/conf/tomcat-users.xml"
/>
Where a softlink was used ( CATALINA_HOME=/usr/local/tomcat ) and tomcat is the
softlink to /usr/local/apache-tomcat-7.0.47 - giving this line
pathname="/usr/local/apache-tomcat-7.0.47/conf/tomcat-users.xml"
it also failed.
The failure is simply a repetition of the request for authentication. Nothing
actually wrong with that part of the process. I am curious what sort of
debugging might enable a check of the login processing itself as enabling debug
down to "fine" still left me with no information that the file was not being
found.
This was discovered by trial and educated guesswork. There is no indication in
the doc that it should be looked at.
A wide range of useless information is out there on the web now, as a lot of
people have this problem in some form. My tomcat-users.xml (when it finally
worked) looks like this:
<role rolename="manager"/>
<role rolename="manager-gui"/>
<role rolename="admin-gui"/>
<role rolename="admin-script"/>
<role rolename="manager-script"/>
<role rolename="manager-xml"/>
<role rolename="manager-status"/>
<role rolename="tomcat"/>
<role rolename="role1"/>
<user username="tomcat" password="tomcat" roles="tomcat"/>
<user username="both" password="tomcat" roles="tomcat,role1"/>
<user username="role1" password="tomcat" roles="role1"/>
<user username="admin" password="tomcat"
roles="tomcat,manager,manager-gui,manager-status,manager-xml,manager-script,admin-gui,admin-script"/>
I have no doubt that a lot of that can be pruned away.
The process in the manual, no matter how carefully followed, does not result in
a working login for the manager.
There may be something more to this. I currently have started tomcat as "root"
which troubles me... but I haven't gotten to the security doc yet and there is
no discussion I've seen that says that manager won't work if you start as
"root" either.
respectfully
BJ
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
