Testing rules

Go to the Latest activity section of your action and you should see a Track a test action button.

Click the Track a test action button and a dialog will pop up where we can provide some test data. Authsignal provides default userId, email, deviceId, userAgent, and ipAddress values but we encourage changing these to test different scenarios.

In the following example, we’ve added a custom data point withdrawalAmount as we have a rule that requires user authentication when the amount exceeds $500.

Click Track action and you will see a breakdown of the action response.

Interestingly, despite our Withdrawing high amount of funds rule being triggered, the action state is Allowed.

The outcome of our rule was ignored because the user is not enrolled (they have not added any authentication methods).

As the user is not enrolled, the url will instead take a user to Authsignal’s pre-built UI enrollment flow.

Let’s enroll the user we used in our test action by clicking the Pre-built UI enrollment URL link and add an authenticator through the pre-built UI.

Now, track another test action with the data we used previously. This time you should see that the action state is Challenge required.

If you want to see a full breakdown of a user action. Refresh the page and you should see the test action you just created in the Latest activity table. Click View details to see the full breakdown of the action.