forcedotcom / forcedotcom/wsc

SoapConnection.java failed to parse response of UNSUPPORTED_CLIENT

Open
#176 0 comments 0 reactions 0 assignees View on GitHub
Work Created
Dominant language
Java
Stars
276
Forks
223
PR merge metrics
No merged PRs in 30d

Description

When the below response comes, SoapConnection.java failed to parse this.

**SOAP Response**
`



sf:UNSUPPORTED_CLIENT
UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https.


UNSUPPORTED_CLIENT
TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https.
https://ap.salesforce.com/secur/weakhttps.jsp?l=1
Stronger security is required




`

**Exception message**
> client.PartnerClient loginInternal (PartnerClient.java:534) - Error while logging in to web service at: https://login.salesforce.com/services/Soap/u/35.0, error was: Failed to parse detail: START_TAG seen ...... @1:752 due to: com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...... @1:752
com.sforce.ws.ConnectionException: Failed to parse detail: START_TAG seen ...... @1:752 due to: com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...... @1:752
at com.sforce.ws.transport.SoapConnection.parseDetail(SoapConnection.java:246)
at com.sforce.ws.transport.SoapConnection.createException(SoapConnection.java:210)
at com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:156)
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:99)
at com.sforce.soap.partner.PartnerConnection.login(PartnerConnection.java:1443)

When accessing organizations that disabled TSL 1.0 through TLS 1.0 or lower protocol, the above situation reproduces.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.