glide.authenticate.multifactor.clock_skewThe glide.authenticate.multifactor.clock_skew property adds extra time in seconds for code validity to account for clock discrepancies. Admins should adjust this setting if users experience issues with multifactor authentication due to time synchronization problems.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property specifies the additional time allowance for multifactor authentication codes to remain valid, accommodating potential clock skew between systems. |
|---|---|
| What area does it affect? | Multifactor Authentication |
| What does the default mean? | The default value is "10", which sets the baseline numeric behavior for this property. |
| When should you review it? | Review this property when users report authentication issues related to time discrepancies. |
Raw metadata from the property record.
| Property name | glide.authenticate.multifactor.clock_skew |
|---|---|
| Sys ID | 64b06d02d7210200700b4187ed61032f |
| Type | integer |
| Application | Global |
| Default value | 10 |
| Description | Additional time in seconds for which the code will be valid to accommodate for the clock skew. Max value is 60 seconds. |
| Updated | 2024-05-25 04:33:16 |