Configure MFA Between Okta and the Firewall

Multi-factor authentication allows you to protect company assets by using multiple factors to verify the identity of users before allowing them to access network resources.
To enable multi-factor authentication (MFA) between the firewall and the Okta identity management service:

Configure Okta

Log in to the Okta Admin Portal to create your user accounts, define your Okta MFA policy, and obtain the token information required to configure MFA with Okta on the firewall.
  1. Create your Okta Admin user account.
    1. Submit your email address and name, then click Get Started.
    2. Click the link in the confirmation email and use the included temporary password to log in to the Okta Admin Portal.
    3. Create a new password that includes at least 8 characters, one lowercase letter, one uppercase letter, a number, and does not include any part of your username.
    4. Select a password reminder question and enter the answer.
    5. Select a security image, then Create My Account.
  2. Configure your Okta service.
    If you log in and are not redirected to the Okta Admin Portal, select Admin at the upper right.
    1. From the Okta Dashboard, log in with your Okta Admin credentials, then select ApplicationsApplications.
    2. Select Add Application.
    3. Search for Okta Verify.
    4. Select Add, then Done.
  3. Create one or more user groups to categorize your users (for example, by device, by policy, or by department) and assign the Okta Verify application.
    1. Select DirectoryGroups.
    2. Click Add Group.
    3. Enter a group Name and optionally a Group Description, then Add Group.
      The default group Everyone includes all users configured for your organization during the first step in Configure Okta.
    4. Select the group you created, then select Manage Apps.
    5. Assign the Okta Verify application you added in Step 2.
    6. After the application has been Assigned, click Done.
    7. Repeat this process for all groups that will use the Okta Verify application for MFA.
  4. Add users and assign them to a group.
    1. From the Okta Dashboard, select DirectoryPeopleAdd Person.
    2. Enter the user’s First Name, Last Name, and Username. The username must match the Primary email, which populates automatically, and the username entered on the firewall. You can optionally enter an alternate email address for the user as the Secondary Email.
    3. Enter the name of the group or Groups to associate with this user. When you start typing, the group name populates automatically.
    4. Check Send user activation email now, then Save to add a single user or Save and Add Another to continue adding users.
  5. Assign a test policy to users.
    1. Select SecurityAuthenticationSign On.
      There is a Default Policy with a Default Rule that does not prompt users to log in with MFA.
    2. Enter the Rule Name and check Prompt for Factor to enforce the MFA prompt, and select the type of prompt (Per Device, Every Time, or Per Session), then Create Rule.
  6. Record the Okta authentication token information in a safe place because it is only displayed once.
    1. Select SecurityAPITokens.
    2. Select Create Token.
    3. Enter a name for the token, then Create Token.
    4. Copy the Token Value.
      You can click the Copy to clipboard button to copy the Token Value to your clipboard.
    5. In the URL for the Okta Admin Dashboard, copy the portion of the URL after https:// up to /admin to use as the API host.
    6. Omit the domain from this URL to use as the Organization.
      For example, in the example Okta Admin Dashboard URL above,
      • The API hostname is
      • The Organization is paloaltonetworks-doc-admin.
  7. Export the Okta certificates using Base-64 encoding:
    1. Depending on your browser, use one of the following methods to export the Okta certificates.
      • Chrome—Press F12, then select SecurityView CertificateDetailsCopy to File.
      • Firefox—Select OptionsPrivacy & SecurityView CertificatesExport.
      • Internet Explorer—Select SettingsInternet OptionsContentCertificatesExport.
    2. Use the Certificate Export Wizard to export the certificates and select Base-64 encoded X.509 as the format.

Configure the firewall to integrate with Okta

As a prerequisite, confirm that you have mapped all users that you want to authenticate using Okta.
  1. Import the certificates on the firewall and add them to a Certificate Profile.
  2. Add a Multi Factor Authentication Server Profile for Okta.
    1. Select DeviceServer ProfilesMulti Factor Authentication.
    2. Add an MFA server profile.
    3. Enter a Profile Name.
    4. Select the Certificate Profile you created in Step 1 in Configure the firewall to integrate with Okta.
    5. Select Okta Adaptive as the MFA Vendor.
    6. Enter the API Host, Token, and Organization from Step 4 in Configure the firewall to integrate with Okta.
  3. Configure Captive Portal using Redirect Mode to redirect users to the MFA vendor’s challenge.
  4. Enable response pages on the Interface Management Profile to redirect users to the response page challenge.
  5. Create an Authentication Profile and add the MFA vendor as a Factor (see Configure Multi-Factor Authentication, Step 3.)
  6. Enable User-ID on the source zone to require identified users to respond to the challenge using your MFA vendor.
  7. Create an Authentication Enforcement Object to use the MFA vendor and create an Authentication policy rule (see Configure Authentication Policy, Steps 4 and 5).
  8. Commit your changes.

Verify MFA with Okta

  1. Verify your users received their enrollment emails, have activated their accounts, and have downloaded the Okta Verify app on their devices.
  2. Go to a website that will prompt the response page challenge.
    If you are using a self-signed certificate instead of a PKI-assigned certificate from your organization, a security warning displays that users must click through to access the challenge.
  3. Log in to the response page using your Okta credentials.
  4. Confirm the device receives the challenge push notification.
  5. Confirm users can successfully access the page after authenticating the challenge by accepting the push notification on their devices.

Related Documentation