Configuring Content Composer Windows Services and Console Applications to Use Hyland IdP - Installation - Foundation 23.2 - Foundation 23.2 - Ready - Content Composer - external

Content Composer Installation

Platform
Content Composer
Product
Installation
Release
Foundation 23.2
License
To configure user-defined Content Composer Windows services to use Hyland IdP authentication, complete the following steps:
Note: These instructions do not apply to the services Composer.Core, Composer.MWS, Composer.OWS, and Composer.XWS.
  1. From the %Composerdir% directory, open the respective CONFIG file with a text editor that supports UTF-8.
  2. Find the <configSections> element and verify that the following line exists within the element.
    <configSections>
    ...
      <section name="userRepository_Idp" type="ModusSuite.Common.SystemFramework.OAuth.IdpConfiguration, ModusSuite.Common.SystemFramework"/>
    ...
    </configSections>
  3. Find the line beginning with <odinSettings configSource=" and verify that the following line exists below.
    <userRepository_Idp configSource = "UserRepository_Idp.config"/>
  4. Find the element <appSettings> and add the following lines within the element. Here, replace Service-IDP-Client-Id with the IdP-Client-ID and idpSecretsFile with the name of the file you created.

    Important: Specify the full file path of the Secrets file. Environment variables are supported.

    <appSettings>
    ...
      <add key="idpClientId" value="Service-IDP-Client-Id" /> 
      <add key="credentials" value="IdpPasswordGrant" />
      <add key="idpSecretsFile" value="%ComposerDir%\idpSecret_JohnMallory.txt" /> 
    ...
    </appSettings>
  5. If you are using authentication type Client Credentials, modify the value of the key credentials to IdpClientCredentials.
    <appSettings>
    ...
      <add key="idpClientId" value="Service-IDP-Client-Id" /> 
      <add key="credentials" value="IdpClientCredentials" />
      <add key="idpSecretsFile" value="%ComposerDir%\idpSecret_JohnMallory.txt" /> 
    ...
    </appSettings>
  6. Find the <runtime> element and add the assemblyBinding element as follows.
    <runtime>
       <generatePublisherEvidence enabled="false" />
       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
             <assemblyIdentity name="Microsoft.Extensions.Logging.Abstractions" publicKeyToken="adb9793829ddae60" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-2.2.0.0" newVersion="2.2.0.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="Microsoft.Extensions.Options" publicKeyToken="adb9793829ddae60" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-2.2.0.0" newVersion="2.2.0.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.2" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="System.Text.Encodings.Web" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="IdentityModel" publicKeyToken="e7877f4675df049f" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-4.6.0.0" newVersion="4.6.0.0" />
          </dependentAssembly>
          <dependentAssembly>
             <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
             <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
          </dependentAssembly>
       </assemblyBinding>
     </runtime>
    
  7. Save and close the file.
  8. Repeat the previous steps for each user-defined Content Composer Windows service and console application.
  9. In Windows Services, change the Log on as property from Local System account to This account using the credentials of the user used to create the Secrets file.