Configure authentication behaviors
Depending on your requirements, you need to configure at least one
authentication behavior. You can configure JWT and Mutual Authentication for a single
property, but you can't mix them in a single request.
Configure the JWT verification behavior This behavior lets you to identify and authorize consumers who send requests to your origin server. You can specify the location in a client request to pass JSON web tokens (JWT), collections of public keys to verify the integrity of these tokens, and specific claims to extract from them. Configure the Mutual Authentication behavior This behavior affects how clients can authenticate themselves to edge servers and how control groups are authorized to access topics. When added, this behavior allows users to authenticate their requests with valid client certificates. It also lets you extract client identifiers or access authorization groups from client certificates and store them as variables for further regex, substring, and hash transformations. Default authorization groups Define a set of default authorization groups added to each request. The default authorization groups work regardless of the authentication method you use, either JWT or Mutual Authentication. Both authentication methods in a property You can configure both JWT and mutual authentication as your authentication methods in a property. You can either configure your authentication methods to overlap and allow one device to make requests with either of them to access different resources, or you can add special rules to your property configuration and allow some devices to use mutual authentication and other devices to use JWTs.