Service Exchange - Catalog Item Images do not sync when glide.attachment.extensions does not have any valueIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The remote catalog item icons/images are not synced from provider instance to the consumer instance. The generic solution for this issue is to whitelist extension property glide.attachment.extensions. But it may create a security concern if one allows all attachment types. The question ,is there a way to add a non extension file type to the list or what is the suggested way to make this work without causing any security concerns? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Service Exchange for consumers Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Clearing glide.attachment.extensions does resolve the sync issue, but that it is not an acceptable long-term solution. it disables attachment type validation entirely rather than permitting the specific files admin needs. Why this happens: The diagnosis is accurate: these image files have no file extension to whitelist. When an image is attached as a catalog item icon, the underlying sys_attachment record is stored without a usable filename extension. During Service Exchange publication, the transport layer passes the filename through as-is; when it is empty, a default placeholder name with no extension is used. On the consumer instance, glide.attachment.extensions validates the incoming file by extension. Because there is no extension, no whitelist entry can ever match it, and the attachment is rejected. This is why emptying the property was the only thing that worked — a blank value disables the check rather than satisfying it. To confirm on the provider instance , below script will output the stored filenames: var a = new GlideRecord('sys_attachment');a.addQuery('table_name', 'sc_cat_item');a.orderByDesc('sys_created_on');a.setLimit(20);a.query();while (a.next())gs.info('name=[' + a.getValue('file_name') + '] type=' + a.getValue('content_type')); Empty or extension-less file_name values confirm the above. Recommended solution— switch to exclusion-list validation Rather than an allow-list you must disable, please use the platform's deny-list model. This keeps protection in place while allowing the icons to sync. Please configure in this order: 1. Set glide.attachment.blacklisted.extensions — the file extensions you want blocked (for example: exe, bat, cmd, sh, js, jar, vbs, dll, msi)2. Set glide.attachment.blacklisted.types — the MIME types you want blocked. This is MIME-based rather than extension-based and is the stronger of the two controls, since extension checks can be defeated by renaming a file3. Only then set glide.security.attachment_type.use_blacklist = true4. glide.attachment.extensions can be restored to its original value; it no longer governs blocking The order matters: enabling the switch before the deny-lists are populated leaves a period where nothing is restricted. This resolves the icon sync because extension-less files are no longer rejected by default, while the file types you consider dangerous remain explicitly blocked.