MFA enforcement properties

Configure the properties for MFA enforcement from Yokohama and upgrade to Yokohama.

To set the MFA enforcement properties, navigate to sys_properties.list to validate or change the MFA enforcement properties.

Table 1. MFA enforcement properties

Field	Description
glide.authenticate.multifactor.setup.bypass.count	Number of times a user can bypass setting up multi-factor authentication (Max possible bypass count is 3, beyond that it will treated as 3).
glide.authenticate.multifactor.self_enrolment_period	Indicates number of days a user will be given an option to self enroll for MFA, post which user will be automatically challenged with MFA. Any value exceeding 90 will be treated as 90 days only.
glide.authenticate.multifactor.enforcement.max_relaxation_period	Indicates the maximum number of days a new user will be given an option to self-enroll for MFA, post which all new user's performing non-SSO logins are automatically challenged with MFA. Any value exceeding 270 is treated as 270 days only.
glide.authenticate.multifactor.enforcement.debug	MFA Enforcement debug logger. Helps in debugging the flows for MFA logins. Note: This property doesn't exist on the instance, you have to create and enable the property, if needed.
glide.authenticate.hybrid_user_tracking.enabled	Property for the tracking of hybrid users. The user accounts which are not marked as 'Web service access only' in corresponding sys_user record, but still performs integrations (For example, API logins) using the username and password, will be tracked in the 'User Login Info' table when this property is enabled. Note: This property doesn't exist on the instance, you have to create and enable the property, if needed.
glide.authenticate.hybrid_user_tracking.debug	A debug logger for the tracking of hybrid user API logins.Side Note: This property doesn't exist on the instance, you have to create and enable the property, if needed.