-
Notifications
You must be signed in to change notification settings - Fork 267
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
fix: select authenticator auto selects when methodType differs #1470
base: master
Are you sure you want to change the base?
Conversation
c3a6930
to
e32e657
Compare
// fix for OKTA-612939 (below) seems to have caused a bug when trying to re-select authenticators | ||
// with multiple methodTypes. If `options.step` is passed, this remediation is explicitly being | ||
// invoked, therefore do not guard against auto-remediating the selected authenticator (OKTA-646147) | ||
if (this.options.step) { |
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.
if (this.options.step) { | |
if (this.options.step || this.values.methodType) { |
What do you think about this fix?
Should cover case if user doesn't provide step
, eg:
await oktaAuth.idx.authenticate({ username: '...', password: '...' })
await oktaAuth.idx.proceed({ authenticator: 'phone_number', methodType: 'sms' })
await oktaAuth.idx.proceed({ authenticator: 'phone_number', methodType: 'voice' })
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.
The fix with step
looks good to me.
What do you think about checking methodType
aswell?
https://github.com/okta/okta-auth-js/pull/1470/files#r1394258583
Please add changelog
'--verbose', | ||
'--disable-dev-shm-usage' | ||
]); | ||
if (process.env.CHROME_BINARY) { |
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.
Do we need to specify CHROME_BINARY
in testenv
locally?
8f99b5a
to
1693e28
Compare
1693e28
to
ac49b6a
Compare
No description provided.