ACL behavior never be the same after High Security rollback

sieusaopolo15
Giga Sage

I am currently working on our Australian non-prod instance. I recently installed the High Security plugin to conduct an impact analysis before deploying it to Production instance.

 

After measuring the impact, I attempted to roll back the plugin because it disrupted several third-party API integrations. However, even after the rollback, the High Security ACL behavior is still there. Specifically, the system still defaults to a 'Deny' state despite the glide.sm.default_mode property being missing from the instance.

 

Before installation, tables without a specific Read ACL—and without a wildcard (*) ACL—defaulted to 'Allow.' Now, the behavior has changed permanently: all tables require a wildcard ACL to be accessible. What am I missing, and is there a way to restore the original security behavior in my non-prod instance ?

1 REPLY 1

Simon Christens
Mega Sage

I would suggest cloning prod to dev and upgrade to Australia again to ensure that the non prod instance reflects the prod instance.
Thats also faster than asking SN Support to restore the DB from an earlier image (this is also a possibility)