JWT Authentication Handler
After the JWT Authentication Handler is installed in DNN, the web.config file is updated with a line similar to the following:
    <authServices>
        <messageHandlers>
            <!-- other message handlers -->
            <add name="JWTAuth" type="Dnn.AuthServices.Jwt.Auth.JwtAuthMessageHandler, Dnn.AuthServices.Jwt" enabled="false" defaultInclude="false" forceSSL="true"/>
        </messageHandlers>
    </authServices>
        | Parameter | Allowed Values | Description | 
|---|---|---|
| name | string | Name of the authentication provider. Must be unique within the messageHandlerssection. | 
| enabled | trueorfalse | If true, an instance of the provider is created and added to the chain of providers when the application starts. Otherwise, the provider is not instantiated. | 
| defaultInclude | trueorfalse | If true, the API controller uses the authentication type included in each Web API request by default; iffalse, the API controller uses the authentication type specified in its ownDnnAuthorizeattribute. Example: If the API controller’s attribute is set to[DnnAuthorize(AuthTypes = "JWT")], then the API controller will respond only to requests that use JWT authentication. | 
| forceSSL | trueorfalse | If true, SSL mode (HTTPS) is required for API requests; otherwise, all requests are accepted.
                Important: To prevent unauthorized access to the site, enforce SSL so that tokens are treated the same way as cookies in a web request.
               | 
      Parent topic: About JWT Authentication
    
  
Priyanka Bhotika
Comments