Closed
Bug 1238925
Opened 10 years ago
Closed 9 years ago
2nd Factor sign-in should have focus on the verification code field
Categories
(Infrastructure & Operations :: SSO: Issues, task)
Infrastructure & Operations
SSO: Issues
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ekyle, Assigned: jabba)
References
Details
Attachments
(1 file)
|
19.56 KB,
image/png
|
Details |
Please have the "additional verification with..." page put the cursor on the password field AND interpret Enter as a click on the "Verify" button. Right now I must click on the password field, press my Yubi key, and then use my mouse to click the verify button.
I would like this page to demand only one action from me: Press the Yubi key button.
| Reporter | ||
Comment 1•10 years ago
|
||
This is the screen I am referring to.
Comment 2•10 years ago
|
||
(In reply to Kyle Lahnakoski [:ekyle] from comment #0)
> AND interpret Enter as a click on the "Verify" button.
This part is bug 1240677, however leaving this bug open for the "give it focus initially" part.
Summary: 2nd Factor sign-in should have focus on password field → 2nd Factor sign-in should have focus on the verification code field
Comment 3•10 years ago
|
||
Hi :-) Is this an issue with Okta or Duo? I don't suppose you could file an upstream ticket for it?
Flags: needinfo?(jdow)
| Assignee | ||
Comment 4•10 years ago
|
||
it's currently a problem with Okta, and there is a fix (switching to Duo native UI), that we are waiting for them to roll out. I believe I can request for it to be rolled out sooner than their natural release cycle though, I'm just trying to work out a communications schedule for it.
Flags: needinfo?(jdow)
Comment 5•10 years ago
|
||
(In reply to Justin Dow [:jabba] from comment #4)
> I believe I can request for it to be rolled out sooner than their natural release cycle
> though, I'm just trying to work out a communications schedule for it.
Ah if you could do that, that would be awesome :-)
Comment 7•10 years ago
|
||
(In reply to Justin Dow [:jabba] from comment #4)
> it's currently a problem with Okta, and there is a fix (switching to Duo
> native UI), that we are waiting for them to roll out. I believe I can
> request for it to be rolled out sooner than their natural release cycle
> though, I'm just trying to work out a communications schedule for it.
(In reply to Ed Morley [:emorley] from comment #5)
> Ah if you could do that, that would be awesome :-)
(In reply to Ed Morley [:emorley] from comment #6)
> Any news on comment 4? :-)
Justin, have you requested for them to roll this out sooner yet?
Thanks :-)
Comment 8•10 years ago
|
||
4 month nudge, similar to bug 1271909 and bug 1240677. (Bugzilla sends daily reminders about these, so they are either being filtered out or ignored)
Flags: needinfo?(jbryner)
| Assignee | ||
Comment 9•9 years ago
|
||
It should be rolled out "soon". I don't know when exactly that will be, but I'm guessing before the end of the year. The recent Auth0 POC and implementation has taken precedent over Okta enhancements.
Flags: needinfo?(jdow)
Updated•9 years ago
|
Flags: needinfo?(jbryner)
| Assignee | ||
Comment 10•9 years ago
|
||
Okta is gone. I think the Auth0 integration with Duo works a bit better.
Assignee: infra → jdow
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•