Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Config Jetty for HTTPS does not work

Description

Hallo OpenNMS-Team,

I wanted to configure OpenNMS for using HTTPS.
Using Wiki-Page: http://www.opennms.org/wiki/Standalone_HTTPS_with_Jetty

Tested own Certificates, then after after a few setbacks, I tested two OpenNMS Servers with example keystore:

cp /opt/opennms/etc/examples/jetty.keystore /opt/opennms/etc/

org.opennms.netmgt.jetty.https-port = 8443
org.opennms.netmgt.jetty.https-keystore = /opt/opennms/etc/jetty.keystore
org.opennms.netmgt.jetty.https-keystorepassword = changeit
org.opennms.netmgt.jetty.https-keypassword = changeit

In every configuration I get no access on https://127.0.0.1:8443/opennms/.
Example Test on bash: wget https://127.0.0.1:8443/opennms/

Additionally I can't find any log Entry in /usr/share/opennms/logs/*

Any Ideas?

Thanks
Helmut

Environment

1x Debian 7.6 / Postgres 9.3 1x Ubuntu 14.04 / Postgres 9.3

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Benjamin Reed August 29, 2014 at 12:01 PM

Also, if you re-run "install" after changing your opennms.config, agalue's jetty config migrator should detect the https bits in opennms.properties and attempt to set up jetty.xml for you.

Markus Neumann August 29, 2014 at 10:41 AM

Markus Neumann August 29, 2014 at 7:34 AM

I have added the work in progress template to the page, including a reference to this issue.
Please feel invited to update the page to match the new configuration approach.

Ron Roskens August 1, 2014 at 9:36 AM

Jetty configuration was recently updated so it uses a jetty.xml instead of programmatically configuring things. The wiki page probably hasn't been updated yet to match reality.

There should be an example jetty.xml in $OPENNMS_HOME/etc/examples/ that you can modify to add an HTTPS listener.

Duplicate

Details

Assignee

Reporter

Due date

Components

Affects versions

Priority

PagerDuty

Created August 1, 2014 at 7:27 AM
Updated January 22, 2015 at 11:48 AM
Resolved January 22, 2015 at 11:48 AM

Flag notifications