UPDATE: RSA Via L&G Integrations with Salesforce Using TLS 1.0 Encryption Protocol
We previously notified you of the potential impact to RSA Via Lifecycle and Governance (RSA Via L&G) customers due to the Salesforce decision to disable the use of the TLS 1.0 encryption protocol for communication with their environments. RSA Via L&G customers that integrate with Salesforce using the product connector and collector capabilities will need to upgrade to an appropriate patch level in order to ensure that their environments are not impacted.
Starting in June 2016, Salesforce will begin disabling the TLS 1.0 encryption protocol using a phased approach. The initial phase in June 2016 is to disable use of TLS 1.0 communication to and from Salesforce sandbox instances. This same change will be phased into Salesforce production instances in early 2017. After Salesforce disables TLS 1.0, any inbound connections to or outbound connections from Salesforce will need to use the TLS 1.1 or TLS 1.2 encryption protocol. This was communicated by Salesforce via the article at the following link:
This change to the Salesforce environments will impact any RSA Via L&G customers using the Salesforce Connector & Collector capabilities available in the product with the AFX or Via Lifecycle functionality.
RSA completed an investigation and verification of the necessary product changes needed to facilitate customer’s use of TLS 1.1/1.2 to integrate with Salesforce via the connectors and collectors. The product changes will be incorporated into upcoming patch releases for versions Via L&G 7.0.0 and IMG 6.9.1. Customers currently on version IMG 6.8.1 and using the Salesforce connector and collector capabilities will need to upgrade to either Via L&G 7.0.0 or IMG 6.9.1.
The delivery schedules for the specific patch releases is currently being reviewed. These patches will be available prior to June 2016.
Customers managing their Salesforce application for their RSA Via Lifecycle and Governance needs can reach out to customer support at firstname.lastname@example.org for any follow up questions.