[Feature] Enable MFA OKTA Push Verification

[eStar386]

Description and related issues - If a user comes to our application having already enabled only push notifications on their Okta account, they will not be able to login with our system. Because of this fact, we should enable push notifications as a MFA factor in our application.

What is the goal or purpose of this ticket? We want to give valid users the easiest time logging in as possible. If they have already set up their Okta account, they shouldn't have to change things in order to use our system.

Acceptance Criteria

• [ ] Given a user has already selected Okta push notifications using Okta, when they log into our system, then they should be able to use their existing account configurations
• [ ] Given a user is signing up for Okta using our system, when they are selecting which MFA option they would like, then they should be provided with all of the same options that they would see in Okta.

This task is done when...

• [ ] push notifications are allowed in our application
• [ ] all acceptance criteria are met

[beparticular]

@tbolt and @eStar386 will take a look and determine if OKTA Verify is something we are or aren't set up to use and what the severity and priority of this bug should be

Updated with notes from discussion and/or parking lot: Context: The site doesn’t display using google authenticator. If the user has a EUA ID existing user and only installed OKTA verify app. What is the intended functionality? Are users required to use google authenticator?

Currently, Google Authenticator is the defacto MFA and for all other updates see note below.

[eStar386]

Update from 05/12 parking @thetif will update issue with relevant information.

[eStar386]

Please note: Currently users with Okta Push setup attempting to access the website using the traditional OTP receive this erroneous message: