Fixes
Resolved Incorrect Error Response for AI-14 Device Connectivity Failures
This release fixes an issue where AI-14 device connectivity failures were incorrectly returned as generic server errors (500) instead of the expected connectivity-specific response (417) after an internal library upgrade, making it difficult to accurately diagnose device connection problems.
With this update:
AI-14 device connectivity errors now correctly return the expected 417 response code, so that integrations and monitoring tools receive accurate status information when a device is offline or experiencing connectivity issues.
Restored HS512 JWT Token Support for GET /organizations/sso API
This release fixes an issue where the GET /organizations/sso API stopped accepting JWT tokens signed with the HS512 algorithm, causing partner SSO authentication requests to fail with a generic 500 (Internal Server Error) instead of completing successfully.
With this update:
The GET /organizations/sso API now correctly accepts JWT tokens signed with the HS512 algorithm, restoring SSO authentication functionality for affected partners. Additionally, error responses have been improved to return more meaningful messages when token-related issues occur.
Admin Pin Improvements
This release fixes an issue where a device that had been offline for an extended period could overwrite newer configuration changes (including admin PIN updates) made via the API while the device was offline, by pushing its stale configuration to the backend upon reconnecting.
With this update:
The system now correctly handles configuration conflicts when a device comes back online, supporting configuration changes made via the API while the device was offline are preserved. Additionally, audit logging has been improved to record only a single entry per configuration change and now includes server and device revision details for better traceability.
GET Driver History API Returning 400 Error
This release fixes an issue where the GET driver-history API returned a 400 error due to incorrect encoding of start and end time parameters in the request, preventing users from successfully retrieving driver history data.
With this update:
The GET driver-history API now correctly encodes time parameters in requests, helping to ensure that driver history queries return accurate results without errors.
​Breaking Changes
JWT Token signature and length change
What's changing
We've updated the JWT token generation process for Partner logins:
- The signing algorithm has been switched from a more permissive standard to a stricter one.
- As a result of this change, the JWT token length has increased.
As part of this change:
- The JWT signing algorithm has been upgraded from a weaker, more permissive standard to a stricter, more secure one.
- This update has resulted in an increase in the overall length of the generated JWT tokens.
- Partners should ensure that their systems can accommodate the longer token length to avoid any integration issues.
Why it Matters
The token-signing algorithm relied on a private-key scheme that was less strict than newer alternatives currently available. Upgrading to a more modern algorithm strengthens its security.