Get OAuth token fails with error 401 Unauthorized since not able to parse the response bodyDescriptionif you have any OAuth provide who sends response body with "content-type" in spite "Content-type" parsing of access token and refresh token will lead to failure and shows 401 Unauthorized errorRelease or EnvironmentReleases after Kingston Patch 0CauseIn the past, in-order to provide support for Mutual Authentication, we introduced a new OAuth Http Client which will be used OOB, this In-house OAuth Http Client has a bug which was discovered newly The discovered bug is that the In-house OAuth Http Client is not able to parse the Content-Type response header because if any OAuth provider sends the response body as "content-type" instead of "Content-Type" parsing of response body is leading to failureResolutionAs a workaround please add below system property and set it to false Name = glide.oauth.inhouse.httpclient.enabledType = true|falseValue = falseAdditional InformationNote: Adding above system property will take ability of using Mutual Authentication Currently this Bug is been handled in PRB1381067.