Adding the admin-settings.json file also enforces sign in on the machine #24286
Description
Is this a docs issue?
- My issue is about the documentation content or website
Type of issue
I can't find what I'm looking for
Description
Hi Team!
We've had a customer who made a good point:
"Today I tested the admin-settings.json to control some of the feature/configuration for our internal users. I tested this on my laptop. I noticed that as soon as I put the configuration file (and restart Docker) it forces me to sign in. I was led to believe through documentation (https://docs.docker.com/enterprise/security/hardened-desktop/settings-management/configure-json-file/) that this wasn't the case, and enforcing sign-in required another configuration. "
Location
Suggestion
We should have a mention somewhere that adding the file also enforces sign-in. Please find the conversation from our engineering team below:
*It also happens when ECI is enabled in the settings
"presence of admin-settings enforces sign-in that is an intended behaviour (its that way since 4.29). Same is true for ECI. i.e. lets say you do not have admin-settings.json, registry.json (or desktop.plist), but you have manually edited settings.json to enable ECI. When you restart DD, you will be asked to sign-in. I think it is implied that if you have enabled a business feature you must sign-in, to continue using DD"
https://docker.slack.com/archives/C91DPPT0W/p1720599296599639?thread_ts=1716915901.884039&cid=C91DPPT0W
https://docker.slack.com/archives/C04K6QQE8PM/p1720517106596439