Swati Gupta (3x Sitecore MVP) | Blogs

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.