Autopush for RADIUS
Okta's Autopush for RADIUS allows you to use the high assurance, low friction Okta Verify with Push feature when it is not possible for an end user to opt-in. The Okta Verify with Push experience has been popular with Admins for its high security implementation. The option for an end user to opt in for an automatic push has also increased end-user satisfaction by removing additional friction; specifically, the extra click to request the push. However, in some use cases, the end user cannot opt in, as this behavior is stored in a browser cookie. To bridge this gap, Okta's Autopush for RADIUS feature permits an admin to configure the behavior without requiring an enduser opt in.
Autopush for RADIUS is compatible with the following:
- Okta VPN integrations supported by RADIUS
- Okta's Generic RADIUS app
Before you begin, complete the following:
Implement either an Okta VPN (using RADIUS) or the Okta Generic RADIUS App in your Okta Preview test environment. See RADIUS Integrations for a complete list of integrations.
- Configure an app-based sign on policy for the application to require MFA on authentication.
- Enable Okta Verify with Push for your Okta preview test environment.
- Assign a test user to the configured app and enroll the test user in Okta Verify.
To enable RADIUS Autopush:
- In Okta, navigate to Applications > Applications.
- Open the target application by clicking its name.
- Select the Sign on tab.
- Scroll down to Advanced RADIUS Settings and click Edit.
- Check the boxes for both of the following items, as shown below.
- Accept password and security token in the same login request
- Permit Automatic Push for Okta Verify Enrolled Users
Note: The first setting is required for autopush. It permits access with alternate MFA if a user has misplaced their device or otherwise lacks access to acknowledge the push.
- Click Save.
Test the integration by performing an authentication with your test user against the configured RADIUS App or RADIUS enabled VPN. No other testing is necessary.