[
https://issues.apache.org/jira/browse/NIFI-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens M Kofoed updated NIFI-7860:
--------------------------------
Description:
I have created a complete new server for NIFI 1.12.0 and created a new
certificate. It is not a wildcard certificate but it has 2 entries (hostname
and fqdn) in dns record. But the server does not start and give an error.
Looking through reported bugs, I found that this issue was allready reported.
Therefore I waited for release 1.12.1
Release 1.12.1 has exactly the same error. I have now created a new certificate
with only the fqdn in the dns entry, and this is working.
So both releases 1.12.0 and 1.12.1 can not handle a private certificate if
there are multiple dns entries.
Sorry for not finding out why, in release 1.12.0, so it could be fixed together
with the other certificate issues which should have been fixed in 1.12.1
was:
I have created a complete new server for NIFI 1.12.0 and created a new
certificate. It is not a wildcard certificate but it has 2 entries (hostname
and fqdn) in dns record. But the server does not start and give an error.
Looking through reported bugs, I found that this issue was allready reported.
Therefore I waited for release 1.12.1
Release 1.12.1 has exactly the same error. I have now created a new certificate
with only the fqdn in the dns entry, and this is working.
So both releases 1.12.0 and 1.12.1 can not handle a private certificate if
there are multiple dns entries.
> Multiple dns records in certificate does not work
> -------------------------------------------------
>
> Key: NIFI-7860
> URL: https://issues.apache.org/jira/browse/NIFI-7860
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.12.0, 1.12.1
> Environment: Ubuntu 18.04 with NIFI 1.12.1
> Reporter: Jens M Kofoed
> Priority: Major
>
> I have created a complete new server for NIFI 1.12.0 and created a new
> certificate. It is not a wildcard certificate but it has 2 entries (hostname
> and fqdn) in dns record. But the server does not start and give an error.
> Looking through reported bugs, I found that this issue was allready reported.
> Therefore I waited for release 1.12.1
> Release 1.12.1 has exactly the same error. I have now created a new
> certificate with only the fqdn in the dns entry, and this is working.
> So both releases 1.12.0 and 1.12.1 can not handle a private certificate if
> there are multiple dns entries.
> Sorry for not finding out why, in release 1.12.0, so it could be fixed
> together with the other certificate issues which should have been fixed in
> 1.12.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
