topic Re: SalesForce updates to SHA-256 in Installing and Upgrading

SalesForce updates to SHA-256

Anonymous — Sat, 16 Nov 2024 11:20:04 GMT

Dear all,
SalesForce is going to update their security certificates to SHA-256.
See also
https://help.salesforce.com/apex/HTViewSolution?urlname=HTTPS-Security-Certificate-Switch-from-SHA-1-to-SHA-256-hash-algorithms&language=en_US
I aked myself which impact this may have on our existing integration so I setup a small tSalesForceConnection job.
My regular login data works fine (connected, job is done). As described here:

As an example, change https://login.salesforce.com/services/Soap/u/32.0 to https://sha2test.salesforce.com/services/Soap/u/32.0 while leaving the path as-is.

I changed the SF URL (note: we use 24.0 instead). I got following error message:

 connected
Exception in component tSalesforceConnection_1
org.apache.axis2.AxisFault: Transport error: 411 Error: Length Required
	at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:310)
	at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:194)
	at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
	at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:404)
	at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231)
	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
	at com.salesforce.soap.partner.SforceServiceStub.login(SforceServiceStub.java:13356)
	at org.talend.salesforce.SforceBasicConnection.renewSession(SforceBasicConnection.java:75)
 disconnected
	at org.talend.salesforce.SforceBasicConnection.init(SforceBasicConnection.java:69)
	at org.talend.salesforce.SforceBasicConnection.<init>(SforceBasicConnection.java:48)
	at org.talend.salesforce.SforceBasicConnection.<init>(SforceBasicConnection.java:25)
	at org.talend.salesforce.SforceBasicConnection$Builder.build(SforceBasicConnection.java:120)
	at salesforce_inxmail.tmp_0_1.tmp.tSalesforceConnection_1Process(tmp.java:319)
	at salesforce_inxmail.tmp_0_1.tmp.runJobInTOS(tmp.java:574)
	at salesforce_inxmail.tmp_0_1.tmp.main(tmp.java:431)

Normally it should be something like invalid user etc.
PS: SalesForce Sandboxes will be migrated to the new certificate on April 1st. All other instances will be changing on August.

Re: SalesForce updates to SHA-256

Anonymous — Thu, 29 Jan 2015 04:01:35 GMT

Hi zo,
Did you try it on latest released version 5.6.1? Have you already created a new feature jira issue for it?
Best regards
Sabrina

Re: SalesForce updates to SHA-256

Anonymous — Thu, 29 Jan 2015 11:02:47 GMT

Hi Sabrina,
yes, I used 5.6.1. and no I didn't create a Jira ticket due to the error message.

Re: SalesForce updates to SHA-256

Anonymous — Thu, 19 Mar 2015 18:06:18 GMT

Has there been any progress on this issue?

Re: SalesForce updates to SHA-256

Anonymous — Tue, 31 Mar 2015 12:24:01 GMT

Hi,
I'm working on Talend ver 4.0.2 and 4.1.2. I have integrations where Talend connects to Salesforce.
I do test whether connection will works after Salesforce certificate change and I've received the same problem with "Length Required" as OZ.
On the Salesforce community I've found suggestion to comment out or delete line with "chunked" parameter in axis2.xml file.
I've done as suggested above, but problem still occurs
Any suggestion what can be done in this case?
Regards,
Lukasz Wrobel

Re: SalesForce updates to SHA-256

Anonymous — Mon, 13 Apr 2015 09:43:48 GMT

Dear all,
still no sucess. same error message occurs; doesn't matter which URL I use - neither https://sha2test.salesforce.com/services/Soap/u/24.0 nor https://gs0.salesforce.com worked. I'm going to wait until sandbox enviroments have been updated and give it then a further try.