[NIFI-5623] Update all usage of Okhttp to latest library

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.0
• Fix Version/s: 1.14.0, 1.13.1
• Assignee: David Handermann
• Reporter: Joe Witt
• Created: 21/Sep/18 17:26
• Updated: 23/Feb/21 14:32
• Resolved: 19/Feb/21 10:43

Description

In looking at existing dep usage and available versions we see

[INFO] com.squareup.okhttp3:mockwebserver ................... 3.6.0 -> 3.11.0
[INFO] com.squareup.okhttp3:okhttp ......................... 3.10.0 -> 3.11.0
[INFO] com.squareup.okhttp3:okhttp .......................... 3.3.1 -> 3.11.0
[INFO] com.squareup.okhttp3:okhttp .......................... 3.6.0 -> 3.11.0
[INFO] com.squareup.okhttp3:okhttp .......................... 3.8.1 -> 3.11.0

But in changing to 3.11.0 it became clear we have work to do so we can better leverage okhttp and its improving/tightening features around things like TLS setup/cert validation/hostname verification. Several tests started failing after the update. We need to use certs with updated SANs and we need to probably improve things as called out in https://issues.apache.org/jira/browse/NIFI-1478.

Issue Links

• incorporates: NIFI-5622 Test certificates require SAN values
• is part of: NIFI-5622 Test certificates require SAN values
• is part of: NIFI-1478 Audit SSLContextFactory and SSLSocketFactory usage throughout application
• is related to: NIFI-8181 Allow users to specify which HTTP Protocol(s) to use with InvokeHTTP
• links to: GitHub Pull Request #4826