Okta single sign-on (SSO) lets users automatically sign in to KnowBe4 Prevent, Defend, and Protect with their Okta credentials on corporate devices. This feature provides easy access to cloud-based applications without additional on-premise components.
Prerequisites
Before you begin configuring Okta, make sure you meet the following requirements:
- Admin access to your Okta organization
- Admin access to your KnowBe4 portal
- Your KnowBe4 regional URL
Configure Okta Application
To create a SAML integration in Okta, follow the steps below:
- Log in to your Okta organization using admin credentials.
- In the admin console, navigate to Applications > Applications.
- Select Create App Integration.
- Select SAML 2.0 as the Sign-in method.
- Click Next.
To configure the SAML integration general settings, follow the steps below:
- Enter an App name.
- Optionally upload an App logo.
- Select Next.
- Enter the Single sign on URL, Audience URI, and Default RelayState for your region:
- Select Show Advanced Settings.
-
Add the following Attribute Statements.
Name Name Format Value http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname Basic user.firstName http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname Basic user.lastName http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress Basic user.email - Select Preview the SAML Assertion to verify your configuration.
- Select Next.
- In the Feedback tab, select I’m an Okta customer adding an internal app.
- Select Finish.
Link Okta to KnowBe4
To locate the Identity Provider metadata URL, follow the steps below:
- In Okta, locate the application you just created.
- Select Sign On.
- Select Identity Provider metadata.
- Copy the metadata URL of the browser that opens.
To link Okta to KnowBe4, follow the steps below:
- Navigate to your KnowBe4 portal:
- In the admin panel, open SSO Configuration.
- Select Use single sign on.
- Enter a provider description. This text will display when users log in.
- In the Metadata URL field, paste the URL you copied from Okta.
- Select Load metadata.
- Select Save.
Configure SCIM Provisioning (Optional)
SCIM provisioning automatically creates and removes user accounts in KnowBe4 based on your Okta directory.
To enable SCIM in KnowBe4, follow the steps below:
- In SSO Configuration, select Enable SCIM provisioning.
- Select Save.
- Copy the SCIM v2 URL and SCIM v2 secret. You'll need these values in the next steps.
To configure provisioning in Okta, follow the steps below:
- In Okta, locate the application previously created and navigate to General > App Settings.
- Select Edit.
- Navigate to Provisioning > Integration > SCIM Connection.
- Select Edit and enter the following:
- SCIM connector base URL: Enter the SCIM v2 URL from KnowBe4.
- Unique identifier field for users: Enter email.
- Supported provisioning actions: Select all options.
- Authentication Mode: Select HTTP Header.
- Authorization: Enter the SCIM v2 secret from KnowBe4.
- Select Test Connector Configuration to verify the connection.
- Select Save.
- Navigate to the Provisioning tab.
- Select Edit.
- Enable the provisioning features you want to use.
- Select Save.
- Scroll down the page to find the Attribute Mappings.
- Keep only the required attributes: username, firstName, lastName, and email.
- Select Save.
To assign uses to the application, follow the steps below:
- In the Okta SSO application, select the Assignments tab.
- Select Assign and choose one of the following options:
- Assign to People to add individual users.
- Assign to Groups to add Okta groups.
- Select the users or groups you want to add.
- Set their username.
- Select Assign.
- Select Done.
Configure Log in to KnowBe4 Email Security Add-In
For users to be able to sign into the KnowBe4 Email Security add-in, the Endpoint URL from the SSO Configuration will need to be used within a registry key to link the add-in and application for authentication.
To enable SSO for the KnowBe4 Email Security add-in, follow the steps below:
- In the KnowBe4 admin panel, navigate to SSO Configuration > Show details.
- Enter the Endpoint URL.
- Deploy the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Egress\Switch HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Egress\Switch
Required values:
| Value Name | Value Data |
|---|---|
| IdentityProviderHost | Enter the Endpoint URL. |
| Server | Enter your Egress server URL:
|