-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Honor store-specific enableOTP setting #261
base: master
Are you sure you want to change the base?
Honor store-specific enableOTP setting #261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good to me, @erayd what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch, thanks 🙂.
also, catch `enableOTP` in `fill` action to copy OTP token after filling login information reference : browserpass#261 (review)
to fetch the `enableOTP` setting reference : browserpass#261 (review)
Ping @erayd if the review request was missed |
Not missed, just short on time. I'm expecting to have some time to spend working on Browserpass during the coming week, which will include this PR. |
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.