Skip to:

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

Wildcard certificate rejected after upgrade from OpenNMS version 26.1.1 to 26.1.2

Description

After upgrade jetty server doesn't start with reason:

Any solution to correct this problem?

Environment

CentOS Linux release 7.8.2003 (Core)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed October 1, 2020 at 8:47 PM

Cool, I'll go ahead and (re-)mark this closed.

Ronny Trommer September 30, 2020 at 7:37 AM

You should buy some beautiful Belgium beer - he figured it out

Cyrille Bollu September 29, 2020 at 10:36 AM

Yes, it works! Even with my full keystore!

Thanks Ronny!

Cyrille

 

Ronny Trommer September 29, 2020 at 9:01 AM

Cyrille Bollu September 28, 2020 at 11:06 AM

Argh damned, I've also run into this bug.

The only workaround I've found is to re-enable HTTP

This error message is very strange because my keystore only contains 1 certificate:

root@opennms:/etc# keytool -list -keystore /etc/opennms/jetty.keystore
Enter keystore password:
Keystore type: PKCS12
Keystore provider: SUN

Your keystore contains 1 entry

opennms-jetty, 28 Sep 2020, trustedCertEntry,
Certificate fingerprint (SHA-256): 9B:01:F1:96:97:C7:B4:B4:33:EB:46:EE:90:89:7A:E4:A4:D8:B8:B4:95:CC:39:FE:17:8E:85:02:28:5F:1D:EF

And, this certificate is really just on single certificate, not a certificate chain.

 

Fixed

Details

Assignee

Reporter

HB Backlog Status

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created July 10, 2020 at 5:31 AM
Updated October 1, 2020 at 8:47 PM
Resolved October 1, 2020 at 8:47 PM