Skip to main content

#TLS0 人正在讨论

Hi,

I found a plugin that let me test my web server to see if it was compatible with TLS 1.2 and it wasn't because the CURL version was't up to date. I was wondering if any one has a test for TLS 1.1 to see if it is compatible? 

5 条评论
  1. 2024年2月7日 15:13

    Thanks for asking. As an update, Salesforce had subsequently phased out TLS 1.1 and has been enabling TLS 1.3. Salesforce supports TLS 1.2 everywhere and, for connections to Salesforce in Hyperforce, TLS 1.3. Connections from Salesforce are presently just TLS 1.2, but Salesforce plans to enable TLS 1.3 for connections from Salesforce in the not-too-distant future. SSL 3.0, TLS 1.0, and TLS 1.1 are permanently off for all uses.

0/9000

Will Social Studio also require TLS 1.1 or above?

4 条评论
0/9000

Hello, for the upcoming TLS 1.0 disablement for Live Agent, is there any way to tell who is still chatting using TLS 1.0? I haven't found any information on the Live Agent objects.

0/9000

We pulled out an email log to verify the TLS Version used and we could see the "TLS_Cipher" & "TLS_Verified". Most of the transactions happened via the TLS1.2 except 3 or 4 which showed as ":" and all the transactions have TLS_Verified as "unverified". Will there be any impact because of the certificate not being verified? What are the steps we need to follow to get it verified. Request your inputs on this.

4 条评论
  1. 2018年3月16日 03:10
    @Vinod Mummareddy Sincere apologies for missing your post ... From what I saw in your log, the messages delivered via TLS 1.0 were all delivered to hosts with IP address in 186.90.28.* ... it is possible that some of the MTAs for your domain support TLS1.1 and higher and some do not. You should speak with your Mail team. Please see the direct message I sent you as well ...
0/9000

Hello All,

  My question related to the TLS 1.0 Disabling is:

 I have the functionality of the "email-to-case" working well right now, the way it works is, the customer send us an email (to our company email server), then, we have configured a redirection to our salesforce mail service email, so the case can be created automatically.

I had validated my company mail server, which have the TLS 1.2, so everything looks ok so far, my doubt is, what happen is the external customer have the TLS 1.0? the case can be created without issues? since the external email are going through our company mail server and the redirection email happens anyway to the salesforce mail service.

 

Or do you think that the external customer also must upgrade to TLS 1.1 + version?

 

Thanks in advance

#TLSemail #TLS #TLS 1.0 Disablement 

3 条评论
  1. 2018年3月2日 21:41
    @Gerald Lizardo Matarranz sorry for the delay in response. On outbound mail from Salesforce, if we cannot negotiate TLS for any reason then we will still send the email but unencrypted (unless you configure your org to require TLS).
0/9000

#TLSemail

#Email 

#TLS 1.0 Disablement 

 

Hi All,

• Can you please help me understand how salesforce decide which version of TSL to use for emails going out of Salesforce application

• Also how salesforce decide which version to TSL to use to emails coming into Salesforce application.

 

We have set TSL Settings as 'Preffered' in your org

0/9000

Hi.

I have done all the required steps to insure that we support TLS 1.1 and above, but received this message from salesforce: "You are receiving this communication because you are the admin of a Salesforce org that is still either sending or receiving emails from your Salesforce org using the TLS 1.0 encryption protocol."

Is this a general message that went out to everyone?

Please advise how I am supposed to proceed.

Thank you

9 条评论
0/9000

#TLSemail 

Hi,

we have been doing some tests and we found an issue that we not understand. 

 

We found a client that is sending to us emails in TLS 1.2 (we know this because the headers) but is not receiving emails when TLS is set as "Required", also we did the test Deliverability to the client and he didn't receiving none of the 32 emails... But when TLS is set as "Prefered" is receiving the 32 emails... 

 

So the conclusion is that we can't trust only see the headers of the incoming email... Am I wrong? Then now we don't know how many clients can be affected to this change... 

2 条评论
  1. 2018年2月8日 07:20
    Hi @Lisa Mac

    , in March, 8 when you do the TLS change this customers are not going to receive any email, right?

    I will open the case anyways.

    Thanks!

0/9000

-- TLS 1.0 Disablement this Weekend --

The following instances will have TLS 1.0 disabled this Saturday, November 11, 2017, at 9:30am US Pacific Time:

 

AP1, AP4, AP5, NA24, NA30, NA49, NA50, NA56, NA59, NA61, NA62, NA99, CS2, CS4, CS5, CS6, CS8, CS14, CS31, CS41, CS43, CS44, CS57, CS58, CS64, CS65, CS98, CS99

 

If you have questions about this change please do not post them as comments on this post. Instead, please create a new post so your question can get the most visibility. We monitor on the Community daily. For the fastest answer, please search this community as your question may have already been answered. Thank you.

TLS 1.0 Disablement Schedule

0/9000

Howdy!  Just confirming that there are no RollupHelper issues related to to the TLS 1.0 disablement.  Correct?   https://help.salesforce.com/articleView?id=000221207&type=1

1 条评论
  1. 2017年11月1日 14:04

    Hello Eric,

    Yes that is correct, our developers have confirmed that there will be no negative effects from the disablement to TLS 1.0 for Rollup Helper.

0/9000