[
https://issues.apache.org/jira/browse/NIFI-16207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104992#comment-18104992
]
ASF subversion and git services commented on NIFI-16207:
--------------------------------------------------------
Commit 8ac3c9a84659a7f55a640f9866c979ea33fa4554 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8ac3c9a8465 ]
NIFI-16207 Switched CaptureChangeMySQL to SSLContextProvider (#11551)
- Required MySQL Connector/J 8.1.0 as the minimum version
- Added DelegatingSSLContextProvider for configuring supplied SSLContext from
SSLContextProvider
> Switch CaptureChangeMySQL to SSLContextProvider
> -----------------------------------------------
>
> Key: NIFI-16207
> URL: https://issues.apache.org/jira/browse/NIFI-16207
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{CaptureChangeMySQL}} Processor currently uses the {{SSLContextService}}
> for direct access to file and password properties for configuring TLS. The
> Binary Log Client can be configured with a custom Socket Factory that aligns
> well with the {{SSLContextProvider}} interface, but the JDBC configuration
> relies on password direct properties.
> The MySQL Connector/J library supports alternative options to supply an
> {{SSLContext}} starting with version 8.1, released in 2023.
> Based on this supported approach, the Processor should be adjusted to use the
> {{SSLContextProvider}} and also require MySQL Connector/J version 8.1 or
> later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
