
Click Cloud To On-Premise link to provide the virtual mapping to the internal system to all the new subaccounts created as the old subaccount. Repeat from step 2 per account associated to the datacenter that you are connected. (Optional) Enter (use the same LocationID that you had previously configured in CIG). Enter the (P-user) and (these are the values you obtained when you enabled CIG). How do I add these new subaccounts into my Cloud Connector? Following are the new subaccounts that customers must register per environment and Data Center:Īll Ariba customers using Cloud Integration Gateway and SAP Cloud Connector in order to integrate their ERP with SAP Ariba solutions. SAP Ariba Cloud Integration Gateway is increasing the number of Cloud Platform Integration (CPI) instances and therefore customers must register these new instances in order to receive documents from all of them. What is the impact if changes are not completed by timeline above?Ĭustomers will not receive some transactions which will be processed by new instances (tenants). What is the deadline to complete this change?Ĭustomers are advised to implement these changes anytime starting today, but they must be completed before Octo11:00 AM PST / 8:00 PM CET Cloud Integration Gateway (CIG) Cloud Connector Configuration Change TLS 1.1 Deprecation and deprecation of select TLS 1.2 Cipher Suites on Octobetween 12:00 PM – 3:00 PM PST/ 9:00 PM -12:00 AM CETģ. TLS 1.1 Deprecation, and TLS 1.2 Cipher Suites Hardening: What customers are impacted and what customer should do?Ģ.
Transport Type should be HTTPS and in the section Connect CIG to Trading Partner, Authentication Type should be Certificate. Go to CIG Menu > My Configurations > Connections Note: How to Identify Certificate based authentication through CIG?
PRODUCTION: will be replaced with and in their test and production environments, respectively. Client Certificates (used for Mutual authentication) / Sign-Verify/Encrypt-Decrypt new URLs are being implemented. Load Balancer certificates (these are used for Customer to Cloud Integration Gateway connectivity) – and and these are not changing. SAP Ariba Cloud Integration Gateway is separating the tenant and the load balancer certificate for the test and production environments respectively due to security standards. This change is for all customer using certificate based authentication or use encryption/signature of their payloads(Suppliers using AS2), this is independently of whatever they use to connect to CIG.ġ2:00pm – 3:00pm PST/ 9:00 PM -12:00 AM CET SAP Ariba Cloud Integration Gateway (CIG) Client Certificate Replacement:
* All the changes were postponed to October 26th - at the same time.