FR: "remember my username" option

[nicotriballier]

I'm submitting a

• [ ] bug report
• [X] feature request

  Background info

Today, from the same device, same browser, end users have to systematically type in their username in the login page. Goal is to eliminate that unnecessary step for subsequent login on the same device/browser.

Expected behavior

• Can we have an option in the sign-in widget so the widget can remember the username, so the user doesn't have to re-enter his/her username at every single login. Expected flow on following sign-in attempts: user goes to the okta login page, username is automatically populated and the widget starts the AuthN flow (no click needed): password, MFA etc.

• Would like to have this ability for both CIAM and Workforce use cases (both using the same sign-in widget library)

• Have the option for admins to automatically select "remember my username" for all users in a given org. End users could unselect it if they want to.

Thanks in advance!

[brettritter-okta]

@nicotriballier - Thanks for the request. I'm a bit confused though, as we do offer a "remember me" feature that stores and populates the username:

This does not include your third bullet point (though we have workarounds), but before digging into those details I want to make sure we are talking about the correct feature.

[nicotriballier]

Hi Brett, today remember me only prefills the username. You still have to click on "next"

Goal is to completely skip the username filling step and go straight to whatever the next step should be (MFA, del-auth to an IDP, x509 cert verification etc.)

thanks

[swiftone]

@nicotriballier - I'll pass the request on, but there are notable UX concerns with putting a (different) user into a state where the first step is backing up - particularly when those steps might be on a different server entirely (such as some MFA/IDP scenarios).

As a workaround I'd expect you can add a piece of JS to the page to detect if the username value is filled in on page load and click the "Next" button for them.

[nicotriballier]

@swiftone thx. FYI this workaround would be feasible in a CIAM scenario since there's a custom DNS and we have full control on the sign-in page html/css/js, but not in a Workforce context where we don't have control on the js code of the page (no custom DNS, no self-hosted sign-in page).