OKTA Integration
OKTA is an OAuth2 authentication service that allows different organizations to be used for authentication in Zus services. By integrating OKTA with Zus, organizations can manage authentication, secure access, and automate user account deletions.
To integrate OKTA with Zus, an organization must follow a structured onboarding process that involves coordination with Zus management and proper configuration of authentication and user management settings.
Below are the steps and required details for setting up an OKTA organization in Zus.
1. Prerequisites
Before integrating OKTA with Zus, organizations must coordinate with Zus management to facilitate the onboarding process. This includes:
Setting up an OKTA organization.
Creating an Admin User who will have full access to all user wallets, including those of deleted users.
2. Required Organization Details
The organization must provide the following details to Zus management to enable integration:
Basic Information
These details will be displayed on Zus services and are essential for the organization’s identity:
Name – The organization's name as it should appear on Zus services.
URL – The official website link of the organization.
Description – A short description of the organization's operations and purpose.
OKTA Application Credentials
These credentials must be retrieved from the OKTA Application Settings page in the OKTA dashboard:
Domain – The organization's domain from OKTA.
Client ID – Unique identifier for the OKTA application.
Client Secret – Secret key associated with the OKTA application for secure authentication.
Admin Client ID – The Admin User's Client ID, specifically created to manage user wallets, even if users are deleted.
Where to Find These Credentials?
Navigate to Okta OAuth2 Manage Dashboard > Applications > Applications > (Selected Application) > Settings
Copy Domain, Client ID, and Client Secret.
Create an Admin User and retrieve its Client ID.
3. Setting Up User Removal Webhook
To ensure account deletions are properly managed, the organization needs to configure a User Removal Webhook in OKTA.
Here are steps to Configure Back-Channel Logout Webhook.
Navigate to Okta OAuth2 Manage Dashboard → Applications → Applications → (Selected Application) → Settings → OpenID Connect Back-Channel Logout.
Locate the "Back-Channel Logout" section. Enter the Webhook URL: Use the Zus-provided webhook endpoint
Select "Selected Initiators Only" in Back-Channel Logout Initiators.
Enable Specific Logout Conditions: Ensure that the following options are selected:
Account Deleted
Account Deactivated
By following these steps, organizations can seamlessly integrate OKTA with Zus, ensuring secure, automated user management.
Last updated