• Make sure that ASE and ABS AI engine communication is disabled. The communication between ASE and ABS is disabled so that no new access log files are sent to ABS AI engine for processing. The training can be reset only when all the access logs available with ABS are processed.
  • Wait for all the access logs available with ABS to be processed.

Use the API with DELETE method when you want to retrain the model with more inclusive API traffic or the API JSON definition has changed in ASE. When an AI model training is reset, all the training data, detected attacks for those APIs and the generated thresholds are lost. However, the metrics data is retained even after the API is retrained. Using the Reset Trained API, you can retrain one or more than one API at the same time. If ABS is deployed in a cluster setup, you can run the API on any of the ABS cluster nodes.

Complete the following steps to retrain the APIs:

  1. Disable access log upload from ASE to ABS by entering the following command on ASE command-line.
    /opt/pingidentity/ase/bin/cli.sh -u admin -p admin disable_abs
  2. Update the API JSON definition in ASE if there are any changes in API.
  3. Run the reset API in ABS.

    The following is the URL for the reset API.

    https://<ABS_host>:<ABS_port>/v4/abs/reset
    • Method: DELETE
    • Body:
      
      {
      “apis” :[“shop”,“electronics”]
      }
      
    Note:

    If you run the reset API when the ABS AI engine is processing access logs, you get an error message with 409 status code.

    {
     “error” : “AI engine is processing access logs; try later. To complete the process, 
      make sure to disable access log upload from ASE. For more information, see the ABS admin guide.”
    }
  4. Wait for the ABS AI engine successfully to reset the APIs.

    You receive the following success message.

    {
     “status” : “API training reset is successful”
    “apis” : [ “shop”, “electronics”]
    }