On August 24 we’ll be releasing an improvement to our security token, further increasing security between Happeo’s connection to Okta and the Azure Active Directory (Azure AD). This update does not affect companies who use Google Workspace as their provisioning system for Happeo.
Please note that if you do not follow these 5 steps before then, your integration with Okta or Azure AD will stop working. As a result, new users will no longer be provisioned into Happeo, and new fields will not be synced, but you will still have access to the platform.
You will likely need an IT admin or someone else in your company who manages your Okta or Azure AD portals. The whole process will not take more than 10 minutes.
The 5 steps to update your Okta/Azure AD security token:
- Go Happeo’s admin panel, click on the “integrations” section and look for the toggle slider that says Okta or Azure AD – you will only see the provisioning system enabled for your platform. This is the active directory that populates Happeo with users from your company.
- Slide the toggle off, wait a minute, then slide it on again. A new security token will appear.
- Copy and paste this security token into Okta or Azure AD’s admin settings. For a more detailed overview, follow the steps in the hyperlinked guides – it’s the same as when you initially set up Happeo.
- Press the “test” button to test the connection. If everything works, save it, and you’re done.
- In the unlikely event that the test fails, please cancel and continue to use the old token, and contact support.
That’s it! You’ll now benefit from a more secure connection between your provisioning source and Happeo.
What will happen to my Happeo integration if I do not update the security token before August 24?
If you fail to update your security token before the deadline, your integration with Okta or Azure Active Directory will stop working immediately. This means that crucial automated directory processes will break down, specifically preventing any new users from being provisioned into your system. In addition, any updates or new directory fields will no longer synchronise between your primary identity provider and the platform.
However, your employees will still have access to the platform during this period. The system itself will remain accessible for daily communication, meaning active users will not be locked out, but the essential background user management and directory syncing features will remain frozen until you complete the update process.
This scheduled update is being released to deliver a significant improvement to the security token. This improvement is designed to further increase the overall security of the connection between the platform and your active directory. Because of these changes, the system requires a newly generated token to establish a secure link.
To avoid any administrative disruption to your provisioning workflows, you must ensure this update is completed before the scheduled date. The entire procedure is straightforward and should not take more than ten minutes of your time, ensuring your platform’s connection remains secure, updated, and fully functional without any prolonged downtime.
Who needs to perform the security token update and are any organisations exempt?
You will likely need an IT administrator or another technical team member who actively manages your company’s Okta or Azure Active Directory portals to perform this update. Because the process requires administrative access to both the internal platform configuration panel and your external identity provider’s settings, standard users will not have the necessary permissions to complete these steps.
This specific security update only affects organisations that rely on Okta or Azure Active Directory as their primary provisioning system. These systems are responsible for populating your platform with user profiles directly from your company’s active directory. If your business uses these tools, coordinate with your IT department to ensure they schedule this ten-minute task before the August deadline.
On the other hand, certain organisations are entirely exempt from taking action. If your company uses Google Workspace as your provisioning system for the platform, this security update does not affect you. Your integrations will continue to function normally without any manual intervention, and you do not need to generate or update any security tokens.
For those who do need to perform the update, it is highly recommended to communicate this requirement to your IT administration team as soon as possible. Providing them with early notice ensures they can log into the respective portals and apply the new security token before the transition date, preventing any disruption to user provisioning.
What are the steps to update the Okta or Azure AD security token?
To update your security token, you must complete five straightforward steps within your administration settings. First, log into the admin panel, navigate to the integrations section, and locate the toggle slider for either Okta or Azure Active Directory. You will only see the specific provisioning system that is currently enabled for your organisation’s platform.
Second, slide this active toggle to the off position, wait for approximately one minute, and then slide it back on again. Performing this action will automatically generate a brand-new security token on your screen. Third, copy this newly generated security token and paste it directly into your Okta or Azure Active Directory admin settings portal.
Fourth, press the test button in your directory settings to verify that the connection works successfully. If the test is successful, save your settings to complete the process. In the highly unlikely event that the connection test fails, you should cancel the operation, continue using your old security token for the time being, and contact customer support immediately for troubleshooting assistance.
This entire process is identical to the steps you followed during the initial configuration of your integration. By completing these quick steps, which take under ten minutes in total, you will successfully establish a renewed and significantly more secure connection between your primary provisioning source and the platform, ensuring ongoing and secure user syncs.
