Actions
Task #10597
closed
Give the ability to enable and configure the tomcat manager when we use the tomcat-multiple-instances role
Status:
Closed
Priority:
Normal
Assignee:
Category:
System Application
Target version:
Start date:
Dec 06, 2017
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Development, Pre-Production, Production
Description
Also, arbitrary additional users and roles must be accepted and managed.
Also, the nginx template used by smartgears must expose the /manager context (with ACLs)
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from New to In Progress
Updated by Andrea Dell'Amico over 7 years ago
The configuration will be global. It will affect all the tomcat instances installed on a node.
Updated by Andrea Dell'Amico over 7 years ago
- % Done changed from 0 to 70
The tomcat part should be complete.
Updated by Andrea Dell'Amico over 7 years ago
- % Done changed from 70 to 100
The smartgears side is also ready to be tested. The template part is:
{% if tomcat_m_manager_install or tomcat_m_host_manager_install %}
{% if smartgears_tomcat_manager_exposed %}
location /manager {
{% for acl in smartgears_tomcat_manager_access_acls %}
{{ acl.policy }} {{ acl.address }};
{% endfor %}
proxy_pass http://127.0.0.1:{{ smartgears_http_port }}/manager;
}
{% endif %}
{% endif %}
So that we have a lot of options:
- activate the manager but do not expose at all
- expose it to a range of addresses
- expose it to the world (this is the default if
smartgears_tomcat_manager_exposedis set toTrueandsmartgears_tomcat_manager_access_aclsis not overwritten)
The defaults are:
smartgears_tomcat_manager_exposed: False
smartgears_tomcat_manager_access_acls:
- { policy: 'allow' address: '0.0.0.0/0' }
Updated by Andrea Dell'Amico over 7 years ago
- Status changed from In Progress to Closed
It's working, just tested on thredds-d-d4s.d4science.org.
Actions
