Condition
Conditions are Boolean logical expressions used to decide the paths between states during a journey or selector execution.
Example of the Condition verifying if mobile phone is currently in the country of residence:
Conditions are usually used to decide how the journey transitions between multiple paths. Since the execution engine requires that exactly one transition needs to evaluate to true in any state with any input, each transition needs to evaluate the same set of context parameters. Given the example above, we will probably need a complementary transition that requires the negated condition. So create a new condition called not_is_phone_in_the_country_of_residence with the following content
not is_phone_in_the_country_of_residenceUsefull conditions
condition name | description |
|---|---|
is_always | Always evaluates to true |
is_never | Always evaluates to false |
is_uba_motion_failed | UBA motion score has a low score. The threshold can be configured inside. UBA scores are between 0 and 1, by default scores grater than 0.5 considered successful passes. |
is_uba_context_failed | UBA context score has a high value (high risk score). values are [0, Infinity). By default a score greater than 5 is considered risky. |
is_specific_application | Validates if the initiating service has the specified name. |
mobile_location_enabled | Checks if the mobile location is enabled |
is_user_in_group | check if the authenticating user is part of a AD group
|
is_authentication_successful | User responded with a valid answer for the current challenge |
is_authentication_failed | User responded with an invalid answer for the current challenge |
is_local_network | The authentication was initiated from the internal network |