Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property controls the evaluation method of View ACLs, allowing for either legacy or updated behavior that aligns with table ACLs. |
| What area does it affect? |
Access Control Lists |
| What does the default mean? |
The default value is "false", which is the baseline setting used unless it is changed. |
| When should you review it? |
Review this property when updating security configurations or troubleshooting access issues related to Views. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.security.expander.view.legacy |
| Sys ID |
17e66d10932212003500db47c47ffb93 |
| Type |
string |
| Application |
Global |
| Default value |
false |
| Description |
This property helps control the way View ACL are evaluated. Setting this property to true will have legacy behavior. Setting this property to false will have the new behavior, which better honor ACL on tables which make up the View. However like before ACL created on View will always override the underlying ACL on tables. |
| Updated |
2024-05-25 04:31:53 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... need to create ACLs on fields in the view. If field-level ACLs exist, the system evaluates them. To require that read ACLs be added to the database views, set the glide.security.expander.view.legacy property to true. On upgraded instances, add this system property and set it to true. When glide.security.expander.view.legacy is true, underlying table ACLs are ignored. When the property is false (the ...
Related properties
More in glide.security
Other properties in the same namespace.
All 45 properties in glide.security →