glide.security.csrf_previous.allowThe glide.security.csrf_previous.allow property permits the use of an expired secure token for validating incoming requests. Admins should consider this setting to enhance security against cross-site request forgery attacks while managing token expiration behavior.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property allows expired secure tokens to be used for request validation, impacting CSRF protection mechanisms. |
|---|---|
| What area does it affect? | Security and Authentication |
| What does the default mean? | The default value is "false", which means this behavior is disabled by default. |
| When should you review it? | Review this property when configuring CSRF protection settings or troubleshooting token validation issues. |
Raw metadata from the property record.
| Property name | glide.security.csrf_previous.allow |
|---|---|
| Sys ID | f9dfac5d0a0a0bb527ed8d28388809e9 |
| Type | boolean |
| Application | Global |
| Default value | false |
| Description | Allow usage of an expired secure token to identify and validate incoming requests. This token is used to prevent cross site request forgery attacks. |
| Updated | 2024-05-25 03:57:49 |
Official references and nearby text excerpts where this property appears.