Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Implemented
-
0.5.0
-
None
Description
The internal use of SSLSocketFactory and SSLContextFactory is inconsistent, as the application has grown around the concept of secure communications. NiFi can act as both a server and as a client for communications, and the default configuration should make it easy for new users to quickly secure the application for incoming and outgoing connections.
In addition, SSLSocketFactory has some inconsistencies and idiosyncrasies which may confuse users [1].
Attachments
Issue Links
- incorporates
-
NIFI-5623 Update all usage of Okhttp to latest library
- Resolved
-
NIFI-1504 InvokeHttp hits NPE if target system doesn't respond with proper HTTPS Headers
- Resolved
- Is contained by
-
NIFI-5458 Improve NiFi TLS and certificate management
- Resolved
- is depended upon by
-
NIFI-1995 Support keystores with multiple certificates by exposing alias selection in configuration
- Open
- is related to
-
NIFI-5176 NiFi needs to be buildable on Java 11
- Resolved
- relates to
-
NIFI-1990 Implement consistent security controls for cluster, site-to-site, and API communications
- Open
-
NIFI-2930 SSLContextFactory throws Exception when Keystore password differs from Key password
- Open
-
NIFI-1444 PostHTTP cannot work with public HTTPS sites
- Resolved
-
NIFI-1688 PostHTTP does not honor SSLContextService Protocols
- Resolved
-
NIFI-1480 Allow different cipher suites configurable properties for NiFi UI & integrations
- Open
-
NIFI-1525 Audit use of private keys throughout application
- Resolved