Part 2: Integrating Content Management Platform with Sitecore Connect Hub: A Step-by-Step Walkthrough

-

Part 2: Integrating Content Management Platform with Sitecore Connect Hub: A Step-by-Step Walkthrough


This blog picks up from where the previous one left off, continuing our discussion on how to proceed with the integration.

  • Now, head over to your Sitecore instance and create a new template in the feature folder. Then, replicate the fields you previously created in Content Hub.
    • .



  • Create a new template in the project folder and inherit the _CMPDemo template that you created in the previous step. Additionally, ensure that it is set to be bucketable.


  • Now, create a page under the Home node using the CMP Demo Details page template. If desired, you can also create a separate template specifically for this page.

  • Navigate to /sitecore/system/Modules/CMP/Config, right-click, and select "Create Entity Mapping." to create a new item 'CMP Demo'.

  • Enter Entity Type Schema, Bucket, Template and Item Name Property.

  • Create a new item using the 'Field Mapping' template for each field.

  • Enter the CMP Field Name and the Sitecore Field Name, ensuring that the CMP Field Name matches exactly with the corresponding field name in Content Hub.

  • Once you create or update anything using that page item, your pages in the content tree will sync with Content Hub. I have created a Request a Demo page in the Content Hub and after syncing I can see it in the Content tree as well.


Comments

Post a Comment

Popular posts from this blog

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine’” on Windows 11

-
Image
Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine' ” on Windows 11 Today I started to install Sitecore 10.2 using Sitecore Instance Manager on Windows 11 and I got this issue “Failed to start service ‘Sitecore Marketing Automation Engine' ” . Error : On event viewer it was showing the below error: I also tried to run ‘ Sitecore.MAEngine.exe ’ like this C:\Windows\system32>C:\inetpub\wwwroot\sclocal102xconnect.dev.local\App_Data\jobs\continuous\AutomationEngine\Sitecore.MAEngine.exe Which was throwing below error: Starting Marketing Automation Engine... 2022-01-29 22:21:11 ERR Error initializing XConnect client. System.AggregateException: One or more errors occurred. ---> Sitecore.XConnect.XdbCollectionUnavailableException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected err
Read more

Azure AD Integration with Sitecore 10.2

-
Image
 Azure AD Integration with Sitecore 10.2 Sitecore identity server that comes with Sitecore 9.1 allows you to log in through an external identity provider like Azure Active Directory, Facebook, Apple, or Google. It is built on Federation Authentication. What is Federation Authentication? Federation authentication is a technology to allows users to access multiples application, tools, and domains using one credential. Using one set of credential user can access multiple applications, and resources after authentication.  Federation authentication consists of two systems, the Identity provider and the Service provider. Identity providers that maintain/create/manage identity information like name, email address, device, and location. Some examples of identity providers are Azure AD, Google, Facebook, and Apple. Service providers basically refer to a website, software, or app that the user is trying to access and SP basically relies on the identity provider to authenticate the user and provi
Read more

Sitecore Custom API Issue with Federation Authentication

-
Image
Sitecore Custom API Issue with Federation Authentication In earlier segments, detailed in Part 1 and Part 2 of the blogs on Keycloak Integration with Sitecore, I introduced Keycloak functionality for CM login. Concurrently, I addressed a necessity to develop custom APIs for retrieving Sitecore users and roles. Following the development of custom APIs, during authentication failures, the API erroneously returned a status code of 200 instead of 401. The problem arose because API requests were being routed through the "owin.identityProviders" pipeline, which was not intended for API usage. Solution: When OWIN identifies a 401 response and the AuthenticationMode is set to "Active," it fails to capture the URL hash included in the request. Another choice is to activate the "Passive" AuthenticationMode, wherein OWIN refrains from actively intercepting 401 responses. In passive mode, your application needs to explicitly issue a Challenge to trigger the OWIN aut
Read more