Due to some missing cryptographic certificates, gridBoxes were unable to establish trusted connections to two public backends required for the integration of the following two asset families:
As a result, gridBoxes were unable to refresh the associated security tokens once those tokens had reached their expiration date.
Affected assets fell back to self-sufficiency optimization during the incident.
Critical cryptographic certificates were accidentally excluded from a software package following an internal change in gridX’s software release process.
The critical cryptographic certificates were restored in the offending software package.
Our alerting was updated to catch asset online/offline status anomalies.