Skip to main content

Update xConnect Certificate in Sitecore Scaled Environment

Update xConnect Certificate in Sitecore Scaled Environment

Recently I have changed the xConnnect certificate for my client, so here are some steps and troubleshooting steps that I have followed for a scaled environment.

Install certificate

  • Double click on your xConnect xxx.xconnect_client.pfx certificate.
  • Select Local Machine and click on Next.

    Update xConnect Certificate in Sitecore Scaled Environment






    Update xConnect Certificate in Sitecore Scaled Environment

  • Enter your password and click on Next.

    Update xConnect Certificate in Sitecore Scaled Environment
  • Select “Place all certificates….” And click on browse and select Personal.


    Update xConnect Certificate in Sitecore Scaled Environment
  • Click on Finish.


    Update xConnect Certificate in Sitecore Scaled Environment


Allow AppPool access to the certificate

  • Go to the certificate and right-click.
  • Go to the All Tasks-> Manage Private Keys.
  • Click on Add and then type “IIS APPPOOL/[APPPool Name]”, click on Check Names, and then click on Ok. I have permitted reporting, reference data, marketing automation reporting, marketing automation, search, processing, collection, and content management.




    Update xConnect Certificate in Sitecore Scaled Environment

Update Thumbprint

Update the thumbprint of the xConnect certificate on the below locations:
  • Update thumbprint on Connection strings of Sitecore Content Management.
  • Update thumbprint on App_Config\AppSettings.config of Collection website:
  • Update thumbprint on App_Config\AppSettings.config of marketing automation website:
  • Update thumbprint on App_Config\ConnectionStrings.config of marketing automation website:
  • Update thumbprint on \App_Data\jobs\continuous\AutomationEngine\App_Config.config of marketing automation website
  • Update thumbprint on App_Config.config\AppSettings.config of processing engine website:
  • Update thumbprint on App_Data\jobs\continuous\ProcessingEngine\App_Config\ConnectionStrings.config of processing engine website:
  • Update thumbprint on App_Config\AppSettings.config of reference data, reporting, and in search  website:
  • Update thumbprint on ConnectionStrings.config of Content delivery website.

Comments

Post a Comment

Popular posts from this blog

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

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...
Post a Comment
Read more

Sitecore Custom API Issue with Federation Authentication

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...
Post a Comment
Read more

Azure AD Integration with Sitecore 10.2

 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 ...
Post a Comment
Read more