[jira] [Updated] (NIFI-5623) Update all usage of Okhttp to latest library

["David Handermann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann updated NIFI-5623:
-----------------------------------
    Affects Version/s: 1.13.0
               Status: Patch Available  (was: In Progress)

PR #4826 upgrades applicable versions of OkHttp to 4.9.1.

The {{nifi-toolkit-api}} generates classes from Swagger definitions and still requires OkHttp 2.7.5.

> Update all usage of Okhttp to latest library
> --------------------------------------------
>
>                 Key: NIFI-5623
>                 URL: https://issues.apache.org/jira/browse/NIFI-5623
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.13.0
>            Reporter: Joe Witt
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)