Jenkins and Tomcat using Reverse-Proxy Auth plugin
Here are the problems I was able to spot:
- You don't need the Reverse Proxy Auth Plugin unless you plan to use Apache or some other web server as a reverse proxy.
There should be a
<security-role> <role-name>Administrator</role-name></security-role>element after the
<login-config>elementC:/Program Files/Apache Software Foundation/Tomcat 7.0/conf/web.xmlis the configuration for Tomcat's "default" servlet, which is used to serve static assets. Adding a security constraint to this servlet causes all the static assets to become inaccessible, which is causing filling your login screen with dead links.
Instead, add the security constraint to C:/Program Files/Apache Software Foundation/Tomcat 7.0/webapps/jenkins/WEB-INF/web.xml
This should just work, but additional changes to C:/Program Files/Apache Software Foundation/Tomcat 7.0/conf/server.xml may be needed to configure the realm. See the Tomcat doc related to this.