AMT Help Files

Application Center BL appsettings

This page lists all the appsettings.json settings available for the Application Center BL (WebApi).

The appsettings.json file is located in the folder <AMT Environment>\AmtTools\ApplicationCenterWebApi\

 

The appsettings file is (sub-)divided into the following sections.

Section Description
AMT The main section where most settings are located.
Logging Section for the logging settings for the Web Application.
AllowedHosts Solo settings which restricts the hosts which may access the Web Application.

 

 

{
  "Amt": {
    "Authentication": {
        },
      }
    }
  },
    }
  },
}


AuthenticationType

The authentication type used to validate tokens received from the Application Center, the only valid option is "JWT" (JSON Web Token).


"AuthenticationType": "JWT",

 

JWT

The 'JWT' section contains settings needed to validate tokens received from the Application Center.


"JWT": {
  "Authority": "https://login.example.org/amt-applications/v2/auth",
  "Audience": "amt-applicationcenter-api",
  "TokenValidationParameters": {
    "NameClaimType": "preferred_username"
  },
  "RequireHttpsMetadata": true
}

 

Logging

Sets the logging levels for the various ASP.NET Core components of the web application. These settings do not need be adjusted in a normal situation.
The allowed log levels are, from most to least detailed: Trace, Debug, Information, Warning, Error, Critical and None.


"Logging": {
  "LogLevel": {
    "Default": "Information",
    "Microsoft": "Warning",
    "Microsoft.Hosting.Lifetime": "Information",
  }
},

 

AllowedHosts

In the AllowedHosts section, access to the web application can be restricted to specific hostnames.
The value is a semicolon-delimited list of host names without port numbers.
By default all hostnames are allowed by the asterisk (*) wildcard.
Disallowed users will get a HTTP 400 error code (Bad Request).


"AllowedHosts": "*",