glide.ui.m.blur_ui_when_backgrounded Problem changing

[Gemma4]

i everyone, 

We are working with our healthscan to make improvements. It was recommended to us to change glide.ui.m.blur_ui_when_backgrounded  property to true to obfuscate fields in snapshot images
on mobile apps. This blurs the screenshots taken by iOS and Android when the app enters the background. 

After setting this property to true and the glide.sg.blur_ui_when_backgrounded property to true, the instance security center is still showing the property as non compliant. See attachments. 

Any thoughts or suggestions how can I make this property compliant? 

Thanks for the feedback!

[Musab Rasheed]

Hello,

Please go through below links to confirm about the behavior, if nothing helps Kindly create HI ticket with Servicenow support team

https://docs.servicenow.com/en-US/bundle/vancouver-platform-security/page/administer/security/refere...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827294

[Floor]

Hi Kilo,

Did you fixed the issue? And how?
I'm having the same issue at the moment and curious how you fixed it

[daware-madhu103]

Hello @Gemma4 Have you found a solution to this problem? I am also experiencing the same problem.  

[Gemma4]

Sorry for the delay in replying. I reached out to support to get this issue resolved. Below are the details, but not sure if this was unique to our environment. Hope this helps but if not it may be helpful to reach out to support as they were very helpful. 

The reason that the "Mobile UI Obfuscation" Security Configuration keeps showing non-compliant is, that the corresponding Dependency Group of this configuration had gone missing:
https://instancename.service-now.com/isc_dependency_groups_list.do?sysparm_query=harc_sec_config%3D6...

Since the group was missing, the regular compliance check for the "Mobile UI Obfuscation" Security Configuration keeps being skipped according to the internal logic. Therefore, the compliance state is not updated.

I have attached the missing Dependency Group in this case. I have also imported the group to your instance for your easier reference. After this, the Security Configuration is now showing as Compliant.

I also dug around for the root cause of the missing group. I believe that the group is missing because it is put in the conditional data of the Instance Security Center plugin and when this plugin was loaded, it did not find the corresponding property and therefore skipped it. This should be a one-off issue related to timing.