Chrome Managed app config - Disable saving passwords

I am trying to find out if anyone else sees this behavior in the managed app config for Chrome.  There is a setting in Chrome app config called "Enable saving passwords to the password manager" this is a Bool entry for True or False.  If I leave it off chrome ignores that setting all together.  If I turn it on and apply it will set that to true, and you can verify with the Chrome://policy in the address bar on the Android device.  If I then set it back to off it shows in the policy as False.  But then if I use a product like Samsung SDSA DataSweeper or send a wipe-application script to chrome it removes that policy all together.  does anyone else have experience with this?  any other settings that I have in Chrome will re-apply to chrome after the wipe.

a year ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
a year ago

Do you really need to wipe the full application? Depending on why you're doing that you may be able to just use clearappcache instead of wipeapplication which will likely leave the app config in tact.

AF
Allen Foster
a year ago

Is Clearappcache new?  I saw it for the first time this past week and I have been managing a SOTI instance for about 8 years now.  We are on 15.6 currently.  If I were using scripting I would switch assuming that is working.  However we use an app that the Samsung SDSA team built called Data Sweeper that does its own wipe application commands.  The idea is that apps get wiped between users.  I know that SOTI 2024 does have some shared device mode stuff built in and we are reviewing that.  As well as looking at Intune with either BlueFletch as the launcher or Managed home screen.  But in all of those instances it does a wipe application not clear app cache.  but that still leaves me with a situation where I have to configure chrome to enable password saving then switch it off to turn that feature off.  otherwise chrome treats it as if that was never set.  Google should have made it a multiple choice with 0,1, or 2 as options.  not just true/false.  Either that or SOTI needs to change the way they implement these managed app configs so that you have to add the key you want to configure, then give it a value.  

AF
Allen Foster
a year ago

also looks like this command is new to 15.6 and only works on devices that use a plugin.  Not Samsung devices.  

RC
Raymond Chan Diamond Contributor
a year ago

How a particular app behaves when its managed configuration parameters get changed with an MDM solution depends solely on the app codes/design and thus corresponding documentation or technical support team of the app of interest should be consulted to ACCURATELY understand the latest expected behaviour, which may be changed between different versions/releases of the same app.

MobiControl "wipeapplication" script command is for cleaning up ALL app-specific data associated with the targeted app, and should very unlikely to be a good way to configure one particular behaviour (e.g. enable/disable saving of passwords to password manager for Chrome in your case) of an app.  It is usually used to restore the app to its very initial state just after all the package binaries got installed when app-specific data fields are either empty or in their default values.  One typical use case is for clean-up of app between log-in/log-out of users on a shared device.   

AS
Alin Sfiriac
a year ago

Did you tried with a profile and add Browser configuration? You can disable Password management, Auto-fill, etc.

I had "hit and miss" with this, sometimes i had to revoke the profile and apply it again so that the settings are applied. 

Looking forward if someone has a fix for this :)

AF
Allen Foster
a year ago

we tried with profile as well.  The same happens when data sweeper runs.  it kills that config to chrome.  

But managed app config should be applied at the next start of the relevant app instantly.

I checked that on several other apps, when i wipe them and restart them they all got the managed app config again when the start up. To be honest i don't have chrome settings to check that way but if Chrome behaves different this could be a topic to investigate with Google (maybe togethet with Soti Support).

C
CKMOD@SOTI
a year ago

Hi Allen,

Thanks for posting on SOTI Pulse.

I would request that you please open a support ticket with the SOTI technical team for more assistance with this issue.

If you have any additional questions or concerns, please don’t hesitate to reach out. We’re dedicated to providing assistance and support.

AF
Allen Foster
a year ago

we have had a ticket open with SOTI on this previously.  Abetech is our hosting partner for our Instance of Soti and they have been working it.  I was interested to see if anyone else in the community saw this same behavior or not.

C
CKMOD@SOTI
a year ago

Hi Allen, 

Thank you for posting on SOTI Pulse.

Has your issue been resolved?

Please let us know if you have any other queries or questions to discuss.

M
MiKe
9 months ago

I want to share my experience with browser configuration (resulting using Chrome). Maybe it will help someone to save a little time.

Customer had quite simple request - 3 bookmarks (ideally shown to the user on app opening), block other urls + disable all fancy browser features (like password and history saving, autofill etc), the only maybe not so common request was to be able to open multiple tabs from each url.

At first I've tried Surf of course but users complained about slow responses and tab/sessions getting logged out on backround.

So I've tried Chrome with browser and bookmarks Profile payloads - unfortunately there is no option to configure homepage for Chrome using Profiles (or I didn't found any).
I've tried to configure it using managed configuration but it's not possible to use both browser&bookmark payload together with managed config so it's either one or another.
As result I've tried to use managed config (bit of PIA ) but there's bug resulting to existence of this thread ( option for disabling saving passwords is being ignored - Soti support provided me workaround which was to 1. Assign Chrome without Appconfig, 2. Remove Chrome with Appconfig, 3. Assign Browser Policy to disable password manage - no I'm not kidding and I've decided not to test it or use it if not absolutly necessary ).

At this point I've tried to use Edge (with Appconfig) - everything seems to be working - more or less - with just one issue - Edge doesn't support opening of favorites/bookmarks using url (edge://favorites/ like on desktop or similar or I failed to found out the correct url - I'm not kidding again). There was light at the end of the tunnel to use Top Sites in New Tab configuration but Microsoft being Microsoft separates Edge configuration policies into device and user ones. And "user or app policy" are only avaliable using MAM (which Soti doesn't support) you can guess easily where can you configure Top Sites :). So I was out of luck again.

Back to the drawing board I found that there is something called Chrome Enterprise Core (for free) so I've tried my luck there. And this is the happy end.. almost. There is also bug that doesn't allows you to configure homepage value starting with "chrome-native://" - as "chrome-native://bookmarks/folder/4" is the URL I need to configure because when you use only chrome:// it won't work correctly (I saved you bit of googling just with this url to the managed bookmarks - you are welcome :). Fortunately there is option to add custom config JSON in the portal so with this final touch I was able to finish my "simple" task.

If someone could tell me how to get rid of the two initial user screens to accept or reject newest advert or what features it would be great

DS
Darren Sandford
8 months ago

I can't provide an answer to your particular problem, but I can share that I've also been frustrated with the shortcomings of 

SOTI Chrome Browser Settings - can't disable prompting for logging in with a google account (we have shared devices and don't want people using their personal google accounts). However, the disable password saving does work.

SOTI Web Filter - can't enable chrome://policy to check settings. Seems to get undone sometimes

Chrome App Policy Managed Config - as highlighted above, the disabling of password saving doesn't work, but the disabling of Brower Sign-in and URL blocking does work.

When I apply a Chrome App Policy Managed Config, it undoes the SOTI Chrome Browser Settings and Chrome Web Filter and allows password saving...so I can't use the Chrome App Policy Managed Config.

SOTI have suggested I only use Chrome App Policy Managed Config, not their settings, but I can't due to the password saving issue.

SOTI Surf is not behaving well with my custom app, meaning that new tabs are launched when I try to logout from app and redirect to logon page, and it keeps me logged in.

I've reported a ticket to SOTI on the Surf issue and I want to use this as my browser, not Chrome, but I currently cannot. 

Not sure how we go about getting Google to resolve the subject of this thread, Chrome App Policy Managed Config not disabling password saving.

Similar Discussions