Comments on: Understanding Adobe’s New Commerce Integration Framework (CIF) https://blogs.perficient.com/2018/06/13/understanding-adobes-new-commerce-integration-framework-cif/ Expert Digital Insights Wed, 20 Jun 2018 21:19:48 +0000 hourly 1 By: Patrick Garcia https://blogs.perficient.com/2018/06/13/understanding-adobes-new-commerce-integration-framework-cif/#comment-18685 Wed, 20 Jun 2018 21:19:48 +0000 https://blogs.perficient.com/adobe/?p=13528#comment-18685 In reply to Nipun Bahri.

Hi Nipun,
Good question and there are several layers to security to be considered. Each namespace with the CIF framework has a corresponding authorization code generated by Adobe specifically for that namespace and organization. To update/create action sequences will require this security auth id. Action sequences can also be versioned to provide backward compatibility to all systems if a major change has been made. Communication between components is via SSL to secure the transport.
Now, most commerce systems also have their own security layers as well. Magento, for example, requires an authorization token to be included in the REST header that corresponds to a guest or registered identity. The same holds true for other commerce platforms as well such as IBM Commerce and Oracle. Configuration connectivity should be managed during the implementation to validate configuration settings such as store id, catalog id, identity can only be retrieved from a valid source.
Hope this helps.

]]>
By: Nipun Bahri https://blogs.perficient.com/2018/06/13/understanding-adobes-new-commerce-integration-framework-cif/#comment-18684 Sat, 16 Jun 2018 13:52:23 +0000 https://blogs.perficient.com/adobe/?p=13528#comment-18684 Hi Patrick, that’s an amazing write up to summarize the integration. One quick query- how do you see the rest API security aspect being handled in this integration ?

]]>