Swati Gupta (3x Sitecore MVP) | Blogs

Unlocking Sitecore Content Hub: A Guide to Utilizing the Web Client SDK - Part 1 Sitecore Content Hub allows connections either through a third-party API or via the Web Client SDK.   Content Hub offers the Web Client SDK, which includes an Entities client for executing CRUD operations—creating, reading, updating, and deleting entities. In this blog, we are going to discuss about Web Client SDK.   Authentication is handled through the OAuth client, which must be set up in Content Hub and then configured on the client side. To create an OAuth client, navigate to the settings and click on OAuth clients. Next, click on the " + OAuth Client" icon to create a new OAuth client. Now, input the Name, Client ID, Client Secret (a randomly generated GUID), and Redirect URL. Develop a fresh console application and incorporate the Web Client SDK NuGet package (Stylelabs.M.Sdk.WebClient). Create a new class named MClientConnector and add the ClientId and ClientSecret that were created in t

Content Hub Insights: Checking Your Sitecore Content Hub Version In previous versions, you could check the Content Hub version by accessing this URL: https://sitecorecontenthubURL/api/status. Visiting this URL would display the product_version. In Sitecore Content Hub, the version was previously displayed, but starting from version 4.2 and above, it will now show the release date. You can find more details here : To check the release date, log in to Content Hub and click the Manage icon on the right-hand side. Now, scroll down to the bottom right corner to see the release date. Also, you can check from this URL https://content-hub-url/api/status/, once you hit this URL then you can check "build_date".

Design Custom Page with Components in Sitecore Content Hub Login into the Content hub, go to Manage and then click the Pages icon. Next, click the right arrow button on Content Pages to display all the child pages under Content. To add new pages, click on the + Page icon. Add the Name, select the Page type, choose the Master layout, and then click the Add button. By default, Header Zone (Left, Right) and Main Zone will display.  You can copy the Header Zone (Left, Right) and Main Zone using the copy icon. You can update the settings by clicking the row settings button. You can delete a row by clicking the delete icon. To add components, click on the + icon and then select the desired component. I selected the HTML component and enabled the Visible option then click on Add button. Click on Edit of HTML component In the HTML component, add your HTML then click on the save button. Make sure the "Appears in menu" option is enabled in the Info tab to display it in the menu. Now &q

Sitecore Content Hub: Method not found: 'Void Microsoft.Extensions.Caching.Memory..." Error While attempting to install Sitecore Connect for Content Hub on-premises, following the instructions outlined in the document located at https://doc.sitecore.com/xp/en/developers/connect-for-ch/51/connect-for-content-hub/install-sitecore-connect-for-content-hub-on-prem.html, on Sitecore 10.3.1, I encountered the following error: In order to address this problem, I investigated the troubleshooting steps for Sitecore Connect for Content Hub. Regrettably, the specific issue was not identified during this process.  Consequently, I raised a Sitecore ticket detailing the problem and provided relevant logs and memory dumps for review.  Upon examination by the Sitecore team, it was discovered that there were two instances of "Microsoft.Extensions.Caching.Memory.dll" within the /bin directory. Both files shared the version number 6.0.0.1, but it was apparent that the instance located i

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

 The Sitecore MVP Award celebrates the most active Community members worldwide who provide valuable online and offline expertise that enriches the community experience and makes a difference. I am pleased to announce that I have been naming a " Most Valuable Professional (MVP) " by Sitecore. After working for more than 8+ years in Sitecore it was fascinating to achieve this milestone which was my dream.  I am really thankful to everyone who has supported me in this journey and guided me. More details about the Sitecore MVP Program you can find  here

Error: Provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted in Sitecore 10.1.2 XP0  While I was installing Sitecore 10.1.2 XP0, I was getting this error "Error: Provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted in Sitecore 10.1.2 XP0". Solution: You'll need to alter two files, namely xconnect-xp0.json and sitecore-xp0.json. Look for occurrences of "Type": "InvokeSqlcmd" in both files, and whenever you encounter a match, include "TrustServerCertificate": true within its "Params" property. Overall, you'll find around 4 or 5 matches within xconnect-xp0.json and 1 match within sitecore-xp0.json where this modification is necessary. Default JSON: Updated JSON: I hope this will solve your issue.