Manage unauthorized access from unmanaged browser

Integrating the Swift Security Extension Inline Hook with Your OKTA Application

Overview

This guide provides step-by-step instructions on integrating a custom inline hook with your OKTA application to ensure users have the Swift Security extension installed in their browser. If the extension is not detected, the user will be prevented from accessing the application after OKTA authentication. This integration is crucial for maintaining security compliance by enforcing the use of the Swift Security extension.

Prerequisites

• Access to OKTA Admin Console

• OKTA API Access Management

• Your application configured in OKTA

Step 1: Create an Inline Hook in OKTA

1. Log in to the OKTA Admin Console:

   • Navigate to your OKTA organization and sign in as an administrator.

2. Go to Inline Hooks:

   • From the Admin Console, go to Workflow > Inline Hooks.

   

   
3. Create a New Inline Hook:

   • Click on the Add Inline Hook button.

   • Select Type as SAML Assertion Inline Hook.

   • Provide a name for the inline hook, such as "Swift Security Extension Check".

4. Configure the Inline Hook:

   • Hook URL: Enter the URL for your custom hook: https://extensionservice-swift.swiftsecurity.ai/hook

   • Authentication Header: If your hook requires authentication, enter the necessary header value.

   • Save the inline hook configuration.

   

Step 2: Integrate the Inline Hook with Your SAML Application

1. Navigate to Your SAML Application:

   • Go to Applications > Applications in the Admin Console.

   • Select the application where you want to enforce the Swift Security extension.

2. Edit the SAML Application:

   • Click on the General tab.

   • Scroll down to the SAML Settings section and click Edit.

3. Add the Inline Hook:

   • Scroll down to the Advanced Sign-On Settings section.

   • Look for the Assertion Inline Hook dropdown.

   • Select the "Swift Security Extension Check" inline hook you created earlier.

4. Save the Changes:

   • Click Next and then Finish to save the SAML configuration.

Step 3: Test the Integration

1. Test Authentication:

   • Perform a test sign-in to the application as a user.

   • If the Swift Security extension is not installed, the user will be prevented from accessing the application, and an appropriate error message will be displayed.

2. Verify Log Entries:

   • You can monitor the logs in OKTA to ensure that the inline hook is being triggered correctly and the extension check is enforced.

References and Further Reading

For more details on configuring inline hooks and SAML applications in OKTA, refer to the following OKTA documentation:

• OKTA Inline Hooks Documentation
• How to Configure SAML 2.0 for Your Application in OKTA
• OKTA API Access Management

Conclusion

By following these steps, you have successfully integrated the Swift Security Extension inline hook with your OKTA application. This ensures that users can only access the application if they have the necessary security extension installed, enhancing the overall security posture of your environment. If you encounter any issues, refer to the OKTA documentation or reach out to Swift Security support for further assistance.