After implementing the custom sign-in widget, users are prompted to enter their password twice. The behavior observed is as follows:
-
The user lands on the sign-in page and enters both username and password, then clicks Sign In.
-
The sign-in widget transitions to the auth beacon and asks for the password again for verification.
- Custom sign-in widget
- Okta SDK
- Factor Sequencing
If the intention is not to present "Password" as a form of extra verification, the behavior can be changed in one of two ways:
-
Locate the Sign-On policy under Security > Authentication > Sign On that is using Password as a secondary form of verification and change the required factor, OR
-
Disable the Factor Sequencing feature under Settings > Features > Factor Sequencing.
NOTE: Only proceed with the second option if the intention is to have factor sequencing disabled for the Org.
If the intention is to present the 2-page login flow to users with Factor Sequencing enabled, ensure the following configuration has been added to the widget code: passwordlessAuth: true.
