Page Comparison

...

1. Appsettings.json

   1. Update these URL’s to match the customer server name

      1. "BaseUrl": "https://unityserver/UnityTest/",

      2. "IdentityUrl": "https://unityserver/UnityTest/"

      3. "PublicOriginUrl": "https://unityserver/UnityTest" **No trailing backslash or Unity app name

   2. Update Log settings - depending on whether you want a lot of logging or the minimum, set appropriately based on the below settings.

      1. For more logging:

         Code Block
         "LogLevel": { "Default": "Debug" "RequestTracingEnabled": true,

      2. For less logging:

         Code Block
         "LogLevel": { "Default": "Warning" "RequestTracingEnabled": false,

   3. Update Application Insights Key (get from dev ops)

      Code Block
      "ApplicationInsights": { "InstrumentationKey": "KEY-HERE"

2. nLog.config - contains more log settings and also the same Application Insights Key as the appsetting.json. Whenever you want to setup more logging, change these settings along with the above and then change them back when you want less logging.

   1. For more logging

      Code Block
      <!--All logs, including from Microsoft--> <logger name="*" minlevel="Trace" writeTo="allfile" />

   2. For less logging

      Code Block
      <!--All logs, including from Microsoft--> <logger name="*" minlevel="Warn" writeTo="allfile" />

   3. Update or add Application Insights key

      Code Block
      <target xsi:type="ApplicationInsightsTarget" name="aiTarget"> <instrumentationKey>KEY-HERE</instrumentationKey> </target>

   4. Set minLevel to “Info' (search file for this as there are several entries that are very similar)

      Code Block
      <logger name="*" minlevel="Info" writeTo="aiTarget" />

3. identity-config.json - this files contains the Unity ClientID, ClientSecret and all the scopes Unity supports. We have a tool that can create the ClientSecret as a hash value so check with Kevin on this.

   1. Update ClientID and ClientSecrets value

      Code Block
      "ClientId": "AWUnity", // a client credentials client "ClientSecrets": [ { "Value": "7m3T***********************OYo=" } ],

   2. Scopes - we don’t typically have to adjust these but we do occasionally add new ones. For example, when AW Payment Plans were added, we added the ‘service.payment’ scope so that needed to be added to each customer using this functionality.

      Code Block
      "Name": "service.payment", "Scopes": [ { "Name": "service.payment" } ] } "AllowedScopes": [ "services", "service.user", "service.customer", "service.entitlement", "service.media", "service.product", "service.order", "service.itinerary", "service.worker", "service.access", "service.contact", "service.account", "service.loyalty", "service.payment" ],

4. Rtp-config.json – contains RTP database, server and SQL login info, as well as RTP admin settings. We occasionally add to the list of settings with new versions and these settings need to be added manually because we do not update the rtp-config.json file with each Unity auto-deployment. Below is a list of settings and descriptions.

...