exceptionfactory opened a new pull request, #9517: URL: https://github.com/apache/nifi/pull/9517
# Summary [NIFI-14001](https://issues.apache.org/jira/browse/NIFI-14001) Adds framework support for PEM private keys and certificates as an alternative to Java Key Stores for TLS communication. The implementation adds `PEM` as a supported value for the following application properties: - `nifi.security.keystoreType` - `nifi.security.truststoreType` Configuring `PEM` for `nifi.security.keystoreType` requires setting the following properties: - `nifi.security.keystore.privateKey` - `nifi.security.keystore.certificate` Configuring `PEM` for `nifi.security.truststoreType` requires setting the following property: - `nifi.security.truststore.certificate` The Administrator's Guide describes the new properties and supported values. The new `certificate` properties support one or more X.509 certificates, separated with newlines, having a `BEGIN CERTIFICATE` header and an `END CERTIFICATE` footer for each certificate included. The new `privateKey` property supports RSA Private Keys encoded according to [RFC 8017](https://www.rfc-editor.org/rfc/rfc8017#appendix-A.1.2) having a `BEGIN RSA PRIVATE KEY` header and an `END RSA PRIVATE KEY` footer. The `privateKey` property also supports private keys encoded according to [RFC 5958](https://www.rfc-editor.org/rfc/rfc5958) having a `BEGIN PRIVATE KEY` header and an `END PRIVATE KEY` footer. PKCS8 private key support includes the following key algorithms: - ECDSA with NIST curves P-256, P-384, or P-521 as described in [RFC 5915 Section 3](https://www.rfc-editor.org/rfc/rfc5915#section-3) - Ed25519 as described in [RFC 8410 Section 10.3](https://www.rfc-editor.org/rfc/rfc8410#section-10.3) - RSA as described in [RFC 8017](https://www.rfc-editor.org/rfc/rfc8017#appendix-A.1.2) The PEM parsing is implemented in the `nifi-security-ssl` module using standard Java security classes without any external dependencies. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [X] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
