Tomcat8 access management page localhost appears: 403 Access Denied

403 Access Denied

You are not authorized to view this page.

If you have already configured the Manager application to allow access and you have used your browsers back button, used a saved book-mark or similar then you may have triggered the cross-site request forgery (CSRF) protection that has been enabled for the HTML interface of the Manager application. You will need to reset this protection by returning to the main Manager page. Once you return to this page, you will be able to continue using the Manager appliction’s HTML interface normally. If you continue to see this access denied message, check that you have the necessary permissions to access this application.

If you have not changed any configuration files, please examine the file conf/tomcat-users.xml in your installation. That file must contain the credentials to let you use this webapp.

For example, to add the manager-gui role to a user named tomcat with a password of s3cret, add the following to the config file listed above.

Note that for Tomcat 7 onwards, the roles required to use the manager application were changed from the single manager role to the following four roles. You will need to assign the role(s) required for the functionality you wish to access.

manager-gui - allows access to the HTML GUI and the status pages manager-script - allows access to the text interface and the status pages manager-jmx - allows access to the JMX proxy and the status pages manager-status - allows access to the status pages only The HTML interface is protected against CSRF but the text and JMX interfaces are not. To maintain the CSRF protection:

Users with the manager-gui role should not be granted either the manager-script or manager-jmx roles. If the text or jmx interfaces are accessed through a browser (e.g. for testing since these interfaces are intended for tools not humans) then the browser must be closed afterwards to terminate the session.

The solution to this problem in general is: vi /usr/local/tomcat/apache-tomcat-8.5.9/conf/tomcat-users.xml Add users and roles in this file:

[root@Dasoncheng2 bin]# vim /usr/local/tomcat/conf/tomcat-users.xml    ##倒数第二行添加
……
<role rolename="admin"/>
<role rolename="admin-gui"/>
<role rolename="admin-script"/>
<role rolename="manager"/>
<role rolename="manager-gui"/>
<role rolename="manager-script"/>
<role rolename="manager-jmx"/>
<role rolename="manager-status"/>
<user name="admin" password="tomcat" roles="admin,manager,admin-gui,admin-script,manager-gui,manager-script,manager-jmx,manager-status" />
</tomcat-users>

But after tomcat8.5 changes, access is still denied.

The following steps are required: vi /usr/local/tomcat/apache-tomcat-8.5.9/webapps/manager/META-INF/context.xml

[root@Dasoncheng2 bin]# vim /usr/local/tomcat/webapps/manager/META-INF/context.xml 
……
<Context antiResourceLocking="false" privileged="true" >
  <Valve className="org.apache.catalina.valves.RemoteAddrValve"
         allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1|192.168.60.*" />  ##这里添加你的ip或网段,可以使用正则;再就是我发现使用192.168.60.0/24这样的方式无法访问!
  <Manager sessionAttributeValueClassNameFilter="java\.lang\.(?:Boolean|Integer|Long|Number|String)|org\.apache\.catalina\.filters\.CsrfPreventionFilter\$LruCache(?:\$1)?|java\.util\.(?:Linked)?HashMap"/>
</Context>

Note: I started to add my own ip address, but I still can't access it. See a post stating that Valve className=”org.apache.catalina.valves.RemoteAddrValve” allow=”127.\d+.\d+.\d+|::1|0:0:0:0:0:0 :0:1” /> Comment out.

[root@Dasoncheng2 bin]# vim /usr/local/tomcat/webapps/manager/META-INF/context.xml 
……
<Context antiResourceLocking="false" privileged="true" >
  <!Valve className="org.apache.catalina.valves.RemoteAddrValve"
         allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1|192.168.60.*" />
  <Manager sessionAttributeValueClassNameFilter="java\.lang\.(?:Boolean|Integer|Long|Number|String)|org\.apache\.catalina\.filters\.CsrfPreventionFilter\$LruCache(?:\$1)?|java\.util\.(?:Linked)?HashMap"/>
</Context>

Then visit http://192.168.5.106:8080/
mark

I think it's a little insecure to comment out this way, all IPs can be accessed and there is no account password (it's useless to add users and roles above)? ?

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325063797&siteId=291194637