ADI Tokens not being recognized when installing the ADI Sync Tool

Incident Report for KnowBe4

Postmortem

On Monday, March 3, 2025, from approximately 7:00 p.m. to Tuesday, March 4, 2025, at 11:40 p.m. (UTC), some customers experienced ADI user provisioning errors.

These issues were caused by a prior update to ADI user provisioning to improve error handling. This update did not account for a certain token validation process, which caused validation errors to occur. To resolve this issue, we improved our code to accommodate the token validation and allow it to pass. The KSAT console loading times returned to normal performance by 11:40 p.m. (UTC).

To prevent this type of issue in the future, we have improved our testing workflows and expanded our testing coverage for error handling and exceptions.

No data loss occurred as a result of this issue.

Posted May 02, 2025 - 20:51 UTC

Resolved

This incident has been resolved.
Posted Mar 05, 2025 - 19:54 UTC

Monitoring

A fix has been implemented for this issue and we are now seeing ADI tokens being accepted during the installation of the ADI Sync Tool.
We will continue to monitor the status of this fix and provide updates as we have them.
Posted Mar 05, 2025 - 12:53 UTC

Investigating

We are receiving reports of ADI tokens not being recognized by the ADI Sync Tool during the installation process. We are looking into this issue and will provide an update once we have more information
Posted Mar 04, 2025 - 20:52 UTC
This incident affected: KnowBe4 Security Awareness Training (KSAT) (User Provisioning).