Welcome to Plumber Configuration Viewer
for Sitecore Commerce

Checking what happens in Sitecore Commerce can sometimes be a bit complicated. This tool will give you insight into how the pipelines are configured, which blocks are used and how the policies are configured per environment.

Plumber connects directly to your Sitecore Commerce Engine instance and doesn't need to be (but can be) installed on a server: Installing Plumber on your own server

To start using Plumber, follow these 3 steps:

1. Configure Identity Server

How to configure Identity Server, depends on the version of Sitecore Commerce you are using. Click one of the buttons below to see the configuration for that version:

Configuration for Sitecore Identity Server on Sitecore Commerce 9.1 or higher

In Sitecore 9.1, Identity Server is used for the whole platform. This brought about a change in the configuration file going from JSON to XML. You can find Identity Server's configuration in the \Config\production folder where Sitecore Identity Server was installed.

Create a new file in this folder called Plumber.IdentityServer.Host.xml and paste the the following xml:


<?xml version="1.0" encoding="utf-8"?>
<Settings>
  <Sitecore>
    <IdentityServer>
      <Clients>
        <PlumberClient>
          <ClientId>Plumber</ClientId>
          <ClientName>Plumber</ClientName>
          <AccessTokenType>0</AccessTokenType>
          <AllowOfflineAccess>true</AllowOfflineAccess>
          <AlwaysIncludeUserClaimsInIdToken>false</AlwaysIncludeUserClaimsInIdToken>
          <AccessTokenLifetimeInSeconds>3600</AccessTokenLifetimeInSeconds>
          <IdentityTokenLifetimeInSeconds>3600</IdentityTokenLifetimeInSeconds>
          <AllowAccessTokensViaBrowser>true</AllowAccessTokensViaBrowser>
          <RequireConsent>false</RequireConsent>
          <RequireClientSecret>false</RequireClientSecret>
          <AllowedGrantTypes>
            <AllowedGrantType1>implicit</AllowedGrantType1>
          </AllowedGrantTypes>
          <RedirectUris>
            <RedirectUri1>{AllowedCorsOrigin}/auth/callback</RedirectUri1>
          </RedirectUris>
          <PostLogoutRedirectUris>
            <PostLogoutRedirectUri1>{AllowedCorsOrigin}</PostLogoutRedirectUri1>
          </PostLogoutRedirectUris>
          <AllowedCorsOrigins>
            <AllowedCorsOrigins1>https://vwr.plumber-sc.com</AllowedCorsOrigins1>
          </AllowedCorsOrigins>
          <AllowedScopes>
            <AllowedScope1>openid</AllowedScope1>
            <AllowedScope2>EngineAPI</AllowedScope2>
            <AllowedScope3>postman_api</AllowedScope3>
          </AllowedScopes>
          <UpdateAccessTokenClaimsOnRefresh>true</UpdateAccessTokenClaimsOnRefresh>
        </PlumberClient>
      </Clients>
    </IdentityServer>
  </Sitecore>
</Settings>

2. Configure Commerce Engine

To configure your engine to allow Plumber to connect to it, you add it as an allowed origin. Open config.json in the wwwroot folder of your commerce engine and add the url of Plumber ( https://vwr.plumber-sc.com) to the AllowedOrigins section. It should look something like this:


"AllowedOrigins": [
   "https://localhost:4200",
   "http://localhost:4200",
   "https://vwr.plumber-sc.com"
],

3. Configure Plumber

Configure Plumber by specifying that Plumber can use to reach the engine and identity server on. Click the button below to open the settings dialog and configure these settings:

Click here for more information on how to configure Plumber