Symptom
- This is to notify on a pro-active basis regarding the Boomi URL TLS V1.1 disablement
- Dates will be announced soon when this change is planned
Environment
Boomi
Cause
This is in accordance with the knowledge base article: 2461964
Below is for the reference why this change is being carried out on Successfactors hosted cloud atoms:
Actions for channels impacted:
SuccessFactors’ OData and SFAPI Integrations
API Integrations are interfaces or applications–including mobile apps and desktop clients–that are separate from SuccessFactors, but use SuccessFactors data. If you have any Boomi, OData and SFAPI Integrations, please ensure that the TLS 1.2 encryption protocols are enabled in those integrations.
Action Required for OData and SFAPI Integrations
If your integrations that use inbound connections to SuccessFactors do not have TLS 1.2 enabled after we make this change, your integrations may experience disruption. We recommend that you begin planning to support TLS 1.2 as soon as possible.
Resolution
We are currently monitoring for all the calls which are coming on TLS 1.1 to Boomi atom URL and judging the impact.
Once the statistics is completed we would announce the dates accordingly.
Firstly Staging atom URL's will be disabled for TLS V1.1 support and within 30 days from this change production atom URL's will also be upgraded
How can we identify if we are using Successfactors boomi cloud atom?
- Goto your Boomi account
- Click on Manage --> Atom Management
- Now click on the atom
- Check the host name linked to the atom
- It will always start with "SF Boomi"
See Also
What if we are using local atoms or Boomi cloud atoms is this change applicable?
- This change which is done is for Boomi atoms hosted by Sucessfactors
If we are using Boomi atom cloud, would this change in Successfactors side, affect our integration?
- Boomi atom cloud already supports TLS 1.1 and above
Keywords
- Boomi cloud atoms TLS 1.1 disablement