Enable Advanced Threat Detection from the Reactor page

[jaywood128]

Enable Advanced Threat Detection from the Reactor page

Problem

Currently, advanced threat detection is enabled on a per-license basis which requires end users to know the system requirements for the minimal amount of resources for heap space ATD takes up.

Solution

Have the Reactor page detect the resources available and render a toggle for Advanced Threat Detection (ATD) on the deployment. This might also make more sense on a customer's account.fusionauth.io page.

On the Reactor page, if sufficient resources are detected, e.g. total memory is 4 GB or greater,

• render an ATD toggle as "Enabled Off" to allow the user to turn ATD on per deployment.
  Insufficient resources detected:
• render an ATD toggle as "Disabled Off"

When the resources are insufficient, hovering on the toggle with the text "Disabled Off" would display a tooltip that says "This deployment doesn't have sufficient resources" to make it clear to the end user why ATD is unavailable. If resources are sufficient on the deployment, default to "Enabled Off".

Alternatives/workarounds

N/A

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

[robotdan]

This could be possible, but there are technical reasons why we must enable this feature on the license server side. FusionAuth doesn't know that it is Enterprise, or Essentials, it just knows which features it can enabled based upon a license.

We can't disable features per node, this would be a very strange user experience to have every n request not work because the feature is not available. When you build a cluster, each node must be sized appropriately.

Separate from sizing concerns, we would want to identify a production use case for disabling ATD at runtime before considering this request.

[matthewhartstonge]

Apologies around terminology - you can replace all references of 'node' to be 'deployment'.

• Disabling ATD in production could be useful due to accidental misconfiguration on initial rollout?