Okta
Last updated
Was this helpful?
Last updated
Was this helpful?
First, navigate in your Okta dashboard to "Applications" and create a new app integration here:
Next, select following options like so:
On the next page, configure the application. Make sure to set the correct Sign-in URIs, those will take the form of <DEFGUARD_DASHBOARD_URL>/auth/callback
(dashboard login) and <DEFGUARD_ENROLLMENT_URL>/openid/callback
(if you want to perform new user enrollment using Okta). Replace <DEFGUARD_DASHBOARD_URL>
and <DEFGUARD_ENROLLMENT_URL>
with the URLs of your Defguard dashboard and enrollment page (proxy) accordingly. If you access your Defguard dashboard at e.g. https://defguard.example.net
your redirect URI will be https://defguard.example.net/auth/callback
.
Next, select the assignment according to your needs, we will select the option that allows every directory member to login:
Now, copy your client ID and secret, as you will need to paste it in your Defguard's settings.
Go to your Defguard settings, and fill all the required information, pasting the Client ID and Client secret from Okta:
The base URL will be based on your Okta domain. In the case of this example, the -admin
part of the URL had to be additionally removed. To additionally verify if your Base URL is correct, you can navigate to <YOUR_OKTA_DOMAIN>/.well-known/openid-configuration
. The issuer field here should be the same as the Base URL.
This feature is available only in Defguard v1.2.3 and above
This documentation concerns only the Okta directory synchronization. For more general information, see the general directory synchronization guide.
The menu can be found in Defguard settings by navigating to the "OpenID" tab.
The following configuration options are currently available in the directory synchronization menu specifically for the Okta provider:
Directory Sync Client ID: The client ID of the Okta directory synchronization app
Directory Sync Client Private Key: The private key of the Okta directory synchronization app
To learn more about the rest of the configuration options, see the general directory synchronization guide.
This feature is currently technically limited to 10000 members or groups. High user or group counts may still trigger your provider API limits even below this threshold. If you have many users (200+), we recommend you test this feature first before you decide to turn on automatic user deletion.
Go to the Okta admin dashboard and navigate to the Applications menu
Make a completely new app integration by clicking "Create App Integration". This app will be solely responsible for communicating with Okta API.
Select "API services"
Name your app integration, e.g. "Defguard directory sync"
Go to your newly created app integration settings and change the client authentication to "Public key / Private key"
Next, click "Add key" and generate a new key pair.
Copy the generated private key in the JSON format to your clipboard
Paste the copied key in the Defguard Okta directory sync settings in the "Directory Sync Private Key" field.
Go back to Okta again. Save your new Okta configuration along with the newly generated keys. Now, copy the app integration's client ID. Paste it in the "Directory Sync Client ID" field in Defguard Okta directory sync settings. Save your Defguard settings.
Return to Okta and under "General settings" turn off the "Require Demonstrating Proof of Possession (DPoP) header in token requests" option. Save your changes.
Now, navigate to the Okta API scopes tab.
Grant the okta.groups.read
and okta.users.read
scopes.
Everything should be set now. Try testing your provider connection in Defguard directory synchronization settings.