Release 2017.1.2 is the third release of OpenNMS Meridian 2017. It is primarily a security and bug fix release.
The codename for 2017.1.2 is Kraków meridian.
Bug
- JMX config GUI can’t connect to JMX service with JNDI name not "jmxrmi" (Issue NMS-8596)
- Tweak Mattermost notification docs not to specify a channel (Issue NMS-9362)
- INFO-level "unable to locate resource" log messages for interfaces not persisted by policy (Issue NMS-9388)
- rescan-exitsing attibute of requisition-def tag in provisiond-configuration.xml is not passed to scanNode() in CoreImportActivities (Issue NMS-9492)
- Northbounders implementation are not sending feedback events for reloadDaemonConfig (Issue NMS-9524)
- XSS: HTML attribute values with quotes not escaped properly (Issue NMS-9645)
- Incorrect logging of exceptions in Slack and Mattermost notifications (Issue NMS-9656)
- IOActive: Reflected Cross-site Scripting in instrumentationLogReader.jsp searchString Parameter (Issue NMS-9672)
- Typo prevents FIQL query values from being URI-encoded (Issue NMS-9694)
- Typo in regional status geo map: Unacknowledges (for unacknolwedged) (Issue NMS-9700)
- Typo: "not elegible" for SNMP primary N enumeration (Issue NMS-9701)
- Duty schedules with embedded newlines break startup (Issue NMS-9709)
- Unexpected errors while generating event definitions from TRAP-TYPE without a DESCRIPTION field (Issue NMS-9718)
- NPE in Enlinkd bridge topology broadcast domain calculation (Issue NMS-9720)
- Null pointer exception in SurvellianceViewConfigurationCategoryWindow.java (Issue NMS-9722)
- ReST v1 does not return errors for unparseable events (Issue NMS-9724)
- Sending bad XML to the Requisitions ReST end point makes the API unusable (Issue NMS-9725)
Enhancement
- ES REST plugin not doing preemptive basic auth (Issue NMS-9699)