- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2024 07:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-21-2024 04:36 AM
Just to make sure, I've contacted ServiceNow Support, and they officially confirmed that once SNC Control Access Plugin gets enabled on the instance, there is no way to roll it back or disable, it is going to be there permanently!
Admins can however add a record with *.* (double asterisk) in the SNC accesses table itself as user name, to allow all servicenow users to by pass this security measure by default. So technically, there is no way to disable the plugin, but practiacally with asterisk we can neutralize it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 05:26 AM
If a production instance doesn't have the activated plugin, but a pre-production instance does, will a clone down from the production instance overwrite/deactivate the plugin? Or is there some auto-activation mechanism that will kick in after the clone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 06:20 AM
If production didn't have snc_access installed, and it is a standard clone, then yes, the plugin will disappear from sub-prod instances along with the list of granted accesses. I've cheked and it was valid behavior upon upgrade from Washington to Yokohama release.
