
tgqft (tgqft) asked a question.
Hello,
I am currently using a Chrome browser (Version 110.0.5481.177) on my Window 10 PC to access my corporate applications via Okta SSO with Okta Verify for 2FA.
At least once a day, I am required to re-authenticate beyond the initial Sign In in the mornings. When prompted to Log-in, my username / password are pre-populated via my LastPass plug-in (as per normal). When clicking the Sign In button, I am not taken to the next page to send the Okta Verify push no matter what. The workaround to this issue that I have found is to clear the Browser cookies.
Example Use Case:
- User signs into Chrome browser using corporate domain email.
- This will bring up an Okta Sign In page
- Complete sign in process via Okta Verify.
- At this point the user is able to launch various SSO base application without additional authentication
- Some hours later while trying to accesses another SSO enabled application i.e. ServieNow
- User is presented with Okta Sign In page
- User will enter user name / password
- Click Sign In
- Nothing happens.
Can anything be done to prevent this behavior.
Thanks,
Victor

Hello @tgqft (tgqft) Thank you for reacting out to our Community!
There could be a number of cases why this happens and this behaviour might be expected behaviour.
We recommend to review the sing in policy's/application policy's and see if the Rule in place is triggered or not.
You might want to take a closer look to see if the users have the ability to "remember MFA" for the session or a period of time.
Please also see our doc here:
https://help.okta.com/en-us/Content/Topics/Security/policies/policies-home.htm
Community members help others by clicking Like or Select as Best on responses. Try it today.