Forcing iManager 2.5 to use a Non-SSL connection (http)

  • 7006112
  • 25-May-2010
  • 26-Apr-2012

Environment

Novell iManager 2.5

Situation

Forcing iManager 2.5 to use a Non-SSL connection (http)
How to connect to iManager 2.5 directly through Tomcat

Resolution

If you want to force iManager to use a non-SSL connection (http instead of https)  You need to edit the webapps\nps\WEB-INF\web.xml file.  At the bottom of the file, locate the <security-contraint> section and place comment tags around the section as shown in RED below:

<!--
<security-constraint>
          <web-resource-collection>
                      <web-resource-name>SSL-requiring Area</web-resource-name>
                      <url-pattern>/servlet/*</url-pattern>
          </web-resource-collection>
          <user-data-constraint>
                      <transport-guarantee>CONFIDENTIAL</transport-guarantee>
          </user-data-constraint>
</security-constraint>
-->

NOTE:  if you make any modifications to the web.xml file, you will need to restart Tomcat for the changes to take affect.


You may also want to bypass Apache altogether and access iManager directly through Tomcat.  You can do this as long as port 8080 is enabled in Tomcat.  In NetWare, port 8080 is disabled by default.  To enable port 8080 on NetWare, you must edit the server.xml file located in the tomcat\4\conf directory.  In the server.xml file, locate the section that has the header of <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->.  You will need to remove the comment tags specified in RED below:

<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->

<!--

<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
                    port="8080" minProcessors="5" maxProcessors="75"
                    enableLookups="true" redirectPort="8443"
                    acceptCount="100" debug="0" connectionTimeout="20000"
                    useURIValidationHack="false" disableUploadTimeout="true" />

-->

NOTE:  if you make any modifications to either the server.xml, you will need to restart Tomcat for the changes to take affect.

If this section is already uncommented, then port 8080 should be listening.  To access iManager 2.5 through port 8080, simply type use the following URL:  http://<ip_address>:8080/nps/iManager.html


Additional Information

This option is not available in the mobile iManager versions
Formerly known as TID# 10096410
Formerly known as TID# NOVL100796

Feedback service temporarily unavailable. For content questions or problems, please contact Support.