Overview
Integrating Swif with Okta allows you to manage user profiles seamlessly by synchronizing data from Okta to Swif. This integration ensures that user profiles are automatically updated, reducing manual data entry and improving data accuracy.
Key Benefits
Automated User Management: Automatically create and update user profiles in Swif based on Okta data.
Secure Data Transfer: Utilize OAuth 2.0 (OIDC) for secure and efficient data synchronization.
Customizable Synchronization: Choose which user data to sync and manage synchronization settings directly from Swif.
How to Set Up the Integration
Step 1: Create an OAuth 2.0 (OIDC) App Integration in Okta
Navigate to Applications: From your Okta Admin Console, go to the Applications section.
Add a New Application: Click Create App Integration and select OIDC – OpenID Connect as the sign-on method and Web Application as Application type
Configure General Settings:
App Name: Name your integration (e.g., “Swif Employee Import”).
Grant Type: Select Refresh Token
Sign-in Redirect URIs: Enter the redirect URI(s)
Trusted Origins: Configure if your platform uses cross-origin requests.
Assign API Scopes:
Add Okta API scopes:
okta.users.read,okta.groups.read.
Assign application permissions to the user who creates the HRIS connection. Otherwise, the user does not have permission to create the connection.
Save the Application: Obtain the Client ID and Client Secret from Okta.
Step 2: Implement OAuth Flow in Swif
Enter Okta Credentials: In the HRIS connection window in Swif, enter the Client ID, Secret, and Okta domain.
Authorize Connection: Swif will use these credentials to authenticate with Okta and establish a secure connection.
Sync User Data: Manually sync user data or enable auto-sync to keep Swif updated with Okta.
Managing the Integration
Connect New HRIS: Click “Connect New HRIS” in Swif to start the integration process.
Submit Okta Credentials: Enter your Okta Client ID, Secret Key, and Domain to establish the connection.
Sync User Data: Manually sync user data or enable auto-sync to keep Swif updated with Okta.
I can't edit the Swif Help Center articles myself because they're hosted outside Atlassian. Below is a section you can paste into both. It's based on https://swifteam.atlassian.net/browse/ST-5666, including its design notes, the backend comments, and Lucas's QA test scenarios.
Auto-sync user groups
You can now keep users and user groups in Swif automatically in sync with Okta. This is useful if you only import certain groups and want Swif to pick up changes as you make them in Okta.
How to set up auto-sync
Choose what to import:
Full import: brings in everyone.
Limited import, by users: you pick specific users.
Limited import, by groups: you pick specific user groups.
Choose whether to turn on auto-sync for that import.
Note: Auto-sync is off by default for new HRIS connections. You need to turn it on yourself.
What auto-sync updates
Import type | New users imported | Existing user details updated (for example, address changes) |
Full import | ✅ | ✅ |
Limited import, users | — | ✅ |
Limited import, groups | ✅ | ✅ |
With auto-sync on for a group, adding or removing users in Okta changes that group's membership in Swif at the next sync.
Selecting groups for a limited import
Groups you've already synced still appear in the group list, with their sync and auto-sync status.
If a group was synced without auto-sync, it's grayed out and can't be selected.
Seeing sync status
HRIS tag: User groups imported from your HRIS have a tag showing where they came from.
Last sync column: The HRIS sync table shows whether the last sync was Full or Limited.
HRIS Details panel: Shows what was added in the last sync:
Full import: which users were synced last.
Limited import: which groups were synced last and which users were added.
Troubleshooting
Ensure that all required scopes and redirect URIs are correctly configured in Okta.
Verify that the Client ID and Secret Key are correctly entered in Swif.
Check network connectivity and permissions if synchronization fails.
For more detailed instructions, refer to the Okta Developer Documentation.