Honor store-specific enableOTP setting #261
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Options allow for the
enableOTP
feature to be specified withinthe
.browserpass.json
, but the feature is not enabled when theoption is specified within
.browserpass.json
and not globally.This was because the check for the setting was only looking for the
global setting -
settings.enableOTP
and did not check for the.browserpass.json
setting (settings.stores[*].settings.enableOTP
).This changeset fixes that issue and properly honors the
enableOTP
setting specified within
.browserpass.json
with or without theglobal
enableOTP
setting.