Property reference

glide.security.multisso.check_table_exists_for_clone

The glide.security.multisso.check_table_exists_for_clone property ensures that the sso_properties table exists when cloning from a non-multisso enabled instance to a multisso enabled instance. This check prevents potential issues after the clone, making it crucial for maintaining system integrity.

Default: true Type: boolean Application: Global

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 enables a check for the existence of the sso_properties table during cloning operations between instances with differing multisso configurations.
What area does it affect? Cloning operations
What does the default mean? The default value is "true", which means this behavior is enabled by default.
When should you review it? Review this property when configuring instance cloning, especially between multisso and non-multisso environments.

Out of the box property record

Raw metadata from the property record.

Property name glide.security.multisso.check_table_exists_for_clone
Sys ID 225e9a609310120016a537ae867ffbdd
Type boolean
Application Global
Default value true
Description When source instance does not have multisso enabled and target instance has multisso enabled during clone, it may result in a bad state after clone so it needs check if table sso_properties exists. When this property presents, it has the patch that does the table existence check.
Updated 2024-05-25 03:38:55

Sources

Official references and nearby text excerpts where this property appears.