Add feature flag to control PIN-only behavior
When the FF is enabled, PIN-only flow becomes available through the setup of pin as a unique factor. Change-Id: Ic71b1a4f50976942c9a1e0dc3c9500f01c2dbfa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5676666 Commit-Queue: Elie Maamari <emaamari@google.com> Reviewed-by: Hardik Goyal <hardikgoyal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1323339}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
e12358f65a
commit
66f83fd4b6
ash/constants
@ -2948,6 +2948,12 @@ BASE_FEATURE(kAuthPanelUsesOnlyPassword,
|
||||
"AuthPanelUsesOnlyPassword",
|
||||
base::FEATURE_ENABLED_BY_DEFAULT);
|
||||
|
||||
// This features controls whether or not passwordless setup is enabled, such as
|
||||
// having a pin-only config.
|
||||
BASE_FEATURE(kAllowPasswordlessSetup,
|
||||
"AllowPasswordlessSetup",
|
||||
base::FEATURE_DISABLED_BY_DEFAULT);
|
||||
|
||||
// Use the staging URL as part of the "Messages" feature under "Connected
|
||||
// Devices" settings.
|
||||
BASE_FEATURE(kUseMessagesStagingUrl,
|
||||
@ -4770,6 +4776,10 @@ bool IsAuthPanelUsingOnlyPassword() {
|
||||
return base::FeatureList::IsEnabled(kAuthPanelUsesOnlyPassword);
|
||||
}
|
||||
|
||||
bool IsAllowPasswordlessSetupEnabled() {
|
||||
return base::FeatureList::IsEnabled(kAllowPasswordlessSetup);
|
||||
}
|
||||
|
||||
bool ShouldEnterOverviewFromWallpaper() {
|
||||
return base::FeatureList::IsEnabled(kEnterOverviewFromWallpaper);
|
||||
}
|
||||
|
@ -939,6 +939,7 @@ COMPONENT_EXPORT(ASH_CONSTANTS)
|
||||
BASE_DECLARE_FEATURE(kUseAuthPanelInSettings);
|
||||
COMPONENT_EXPORT(ASH_CONSTANTS)
|
||||
BASE_DECLARE_FEATURE(kAuthPanelUsesOnlyPassword);
|
||||
BASE_DECLARE_FEATURE(kAllowPasswordlessSetup);
|
||||
COMPONENT_EXPORT(ASH_CONSTANTS) BASE_DECLARE_FEATURE(kUseLoginShelfWidget);
|
||||
COMPONENT_EXPORT(ASH_CONSTANTS) BASE_DECLARE_FEATURE(kUseMessagesStagingUrl);
|
||||
COMPONENT_EXPORT(ASH_CONSTANTS)
|
||||
|
Reference in New Issue
Block a user