Onboarding Users onto Dune Security from Okta

Complete API token creation, SSO setup, and SCIM provisioning.

This guide will walk you through the process of integrating Dune Security with Okta for seamless user onboarding and identity management. Follow these steps to ensure a smooth setup and optimal performance of Dune Security within your organization.

Overview

Integrating Dune Security with Okta enables you to leverage Okta’s robust identity and access management capabilities to manage your Dune Security users. This integration supports automated user provisioning, single sign-on (SSO), and enhanced security controls.

Pre-Session Requirements

Before beginning the onboarding process, ensure that you have:

1. Admin access to your Okta tenant.
2. Admin access to your Dune Security account.
3. API tokens and necessary credentials for both Okta and Dune Security.

Step-by-Step Guide to Onboarding Users

1. Set Up Single Sign-On (SSO) with Okta

1. In Okta Admin Console:
   • Navigate to Applications > Applications.
   • Click Add Application.
   • Select Create New App.
   • Choose Web as the platform and SAML 2.0 as the sign-on method.
   • Click Create.
2. Configure SAML Settings:
   • App name: Enter "Dune Security SSO".
   • Single Sign-On URL: Enter the ACS URL from your Dune Security platform.
   • Audience URI (SP Entity ID): Enter the Entity ID from your Dune Security platform.
3. Attribute Statements:
   • Name: email
   • Name format: Unspecified
   • Value: ${user.email}
4. Click Next, review the configuration, and click Finish.
5. Assign the Application to Users:
   • Go to the Assignments tab in the Dune Security SSO application.
   • Assign the application to users or groups as needed.
6. Download the Identity Provider metadata file from the SSO configuration page in Okta and upload it to the Dune Security admin console under the SSO settings.

2. Provision Users from Okta to Dune Security

1. Enable SCIM Provisioning in Okta:
   • Navigate to the Dune Security SSO application in Okta.
   • Under the App Settings, enable SCIM Provisioning.
   • Go to the Provisioning tab.
   • Click Configure API Integration.
   • Enable API Integration and enter the SCIM API base URL: https://scim.dunesecurity.io/scim/v2.
   • Unique Identifier Field: email
   • Select all options for supported provisioning actions.
   • Authentication Mode: HTTP Header
   • Enter the SCIM API token obtained from Dune Security under Authorization.
   • Click Test API Credentials to verify the connection.
   • Save the configuration.
2. Configure Provisioning Settings:
   • Enable Create Users.
   • Enable Update User Attributes.
   • Enable Deactivate Users.
3. Map User Attributes:
   • Ensure the attributes from Okta match the required attributes in Dune Security.
4. Assign Users and Groups for Provisioning:
   • Go to the Assignments tab in the Dune Security SSO application.
   • Assign the appropriate users and groups that you want to provision to Dune Security.

Post-Setup Verification

1. Test SSO Login:
   • Ensure users can log in to Dune Security using Okta SSO by navigating to the Dune Security login page and selecting the Okta SSO option.
2. Verify User Provisioning:
   • Check the Dune Security admin console to ensure that users and groups from Okta are correctly provisioned.
3. Monitor and Troubleshoot:
   • Regularly monitor the integration logs in both Okta and Dune Security for any issues or errors.
   • Contact Dune Security Support for any assistance or troubleshooting needs.

Next Steps

Next, ensure email deliverability of phishing assets to your users. Choose the appropriate guide for your email provider:

1. Whitelist Domains and IP Addresses in Microsoft 365
2. Implement DMI through Your Google Workspace to Ensure Email Deliverability