Unlocking Sitecore Content Hub: A Guide to Utilizing the Web Client SDK - Part 1

-

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 the previous steps.
     

    • Next, in the Program.cs file, call the TestConnectionAsync function.

    • Now run the console application.



    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