Okta IdP with a protected app through Okta Access Gateway

OPSWAT MetaAccess can be easily integrated with an existing Okta Access Gateway to ensure that a device is compliant with the organization's security policy before it is granted access to protected applications which connected with Okta Access Gateway. This ensures that the device is not only authenticated by the IdP, but also tested for risks and vulnerabilities such as infections or unpatched versions of operating systems BEFORE it accesses an organization's on-premise applications.

To get started with implementing OPSWAT MetaAccess integration to enforce device posture check before granting a device to access protected applications with Okta Access Gateway, you need to have your protected app configured on Okta Access Gateway and configured Okta tenant as an IdP for Okta Access Gateway. If you haven't already done so, please follow the instructions on Okta Help Center to add your applications to Okta Access Gateway.

Note: Please be aware that this integration needs to update SAML settings of the protected app on Okta, and you need to re-do that if you make any changes of the app on Okta Access Gateway to make sure that a connection between Okta and OPSWAT MetaAccess still exists.

You can learn more details for each step here at 3.1.1. How to set it up?

Step 1. Enable Access Control on your MetaAccess account

  1. Login to the MetaAccess console

  2. Navigate to Access Control and then Configurations

  3. Check on "Enable access control" and configure a port for the cross-domain API. Note that you must select a port which no applications on endpoints are running.

  4. Click SAVE.

    images/download/attachments/342578/image2018-3-9_13-43-24.png

Step 2. Import Identity Providers and Applications

  1. Download Okta IdP certificate: the next step is importing an Okta X.509 certificate to MetaAccess. This allows MetaAccess to verify users signing though a trusted IdP, Okta. Each identity provider has a unique X.509 certificate. Download the Okta X509 certificate by following these steps:

    1. Log into Okta as Administrator

    2. Switch to Admin mode

      images/download/attachments/342578/image2017-10-17_16-0-11.png
    3. Go to Applications dashboard

      images/download/attachments/342578/image2017-10-17_16-0-41.png
    4. Select your application

    5. Go to Sign On tab and click View Setup Instruction
      images/download/attachments/342578/image2019-11-26_15-41-16.png

    6. Click Download certificate to download Okta certificate

      images/download/attachments/342578/image2019-11-26_15-42-52.png

  2. Collect the application ACS URL and IdP SSO login URL

    • In Okta Administrator console, select Applications, then select your protected application

    • The Assertion Consumer Service URL is the Single sign on URL on the SAML Settings section on the General tab

images/download/attachments/342578/image2019-11-26_15-33-45.png

  • on the General tab, scroll down to App Embed Link section,

  • The IdP SSO login URL is the embed link

images/download/attachments/342578/image2019-11-26_15-38-50.png

4. Add the Okta Identity Provider. If you already have Okta IdP settings on your MetaAccess account, go to step 2.5 to add your application.

  • Login to the MetaAccess console

  • Navigate to Access Control and then Configurations

  • On the Identity Providers tab, click "Add New Identity Provider" to add your IdP

  • Fill in required fields for the Identity Provider

    • IdP Name: an IdP name, for example, Okta

    • IdP Certificate: upload Okta certificate you downloaded in Step 2.1

      images/download/attachments/342578/image2019-11-15_12-27-11.png

  • Click Add IDP

  • Click SAVE CHANGES

5. Add your protected application:

  • Expand the Okta IdP settings you have just added in Step 2.4 above.

  • Click Add New Application

  • Fill required fields. Other optional settings are in the Advanced Settings

    • Application: application name, for example, Protected Application

    • IdP Login URL: IdP SSO login URL which you have from step 2.2

    • Application Login URL: application login URL which you have from Step 2.2

    • Access Mode: pick an access mode you prefer. See details on the access modes at Step 2. Import Identity Providers and Applications

      images/download/attachments/342578/image2019-11-26_15-47-27.png
  • Click SAVE CHANGES

6. After saving your changes successfully, click Setup Instructions of your application, you have just added and then copy the URL MetaAccess generated there. This URL is used to replace Single sign on URL of the application on Okta in Step 4.

images/download/attachments/342578/image2019-11-26_15-50-0.png

Note: you can add your application (step 2.5) when you add Okta IdP settings.

Step 3. Configure Access Rules

  1. On MetaAccess console, navigate to Access Control and then Configurations

  2. On Access Rules tab, click "ADD NEW RULE" to add a new rule for this application OR you can update existing access rules to add this application

  3. With a new access rule, you need to specify how you would like to block/allow access a device from the application

    1. Rule name: a rule name, for example Block non-compliant devices

    2. Action: Block or Allow

    3. Configure conditions to do the action. Details at Step 3. Configure Access Rules

  4. Click ADD RULE

    images/download/attachments/342578/image2018-3-9_13-55-33.png

Step 4. Update Applications settings on Identity Provider

  1. Login to Okta as administrator

  2. Navigate to Applications dashboard

  3. Select your application

  4. On General tab, click Edit on the SAML Settings section

images/download/attachments/342578/image2019-11-26_15-51-53.png

5. Click Next on the first screen

  • uncheck " Use this for Recipient URL and Destination URL" option first so that we can configure different URL for Single sign on URL and recipient URL.

  • replace Single sign on URL with the MetaAccess URL which you got from Step 2.6

images/download/attachments/342578/image2019-11-26_15-56-54.png

6. Click Next

7. Click Finish

Step 5: Test your integration

Follow guideline here to test your integration to verify if it works as your expectation.

DONE! CONGRATULATIONS.