Skip to content
Identity and Access Management

02 July 2025

Production release: 02 July 2025
Staging release: 23 May 2025

30 June 2025

Section titled “30 June 2025”

Enhancements

Section titled “Enhancements”

  • To support the existing functionality in TID MyProfile where the state field is mandatory for users in the US and Canada and live-synced to Profiles, the IAM normal and managed user creation/mutation APIs will now enforce state validation when the country is US or CA. Therefore, the State field must always be provided during user creation and mutation if the selected country is US or Canada. Please refer IAM Documentation page for more details.

  • Moving forward, the query parameter for retrieving full organization details via GET /organizations/{organizationId} will transition from fields=full to include=full. This update standardizes the API’s behavior with other Identity and Access Management (IAM) APIs, such as GET /accounts?include=roleIds,externalSystems, promoting consistency and ease of use.

  • The create organization API to allow users of account type dealer (as determined from the accountId from the JWT) to bypass the standard authorization check for the ‘organization: create’ permission. With this update, a dealer can directly access the API without requiring explicit permission assignment.

  • We’ve enhanced our existing permission API! While you can already GET /permissions/{permissionId} to retrieve permission details, we’ve now added a new capability. You can now directly check if a subject has a specific permission on a particular target entity using the GET /permissions//isAllowed?subject=&on= endpoint.

Bugfix

Section titled “Bugfix”

  • During account searches, a set of issues were identified, specifically concerning cosmetic problems with validation exception messages and the 500 error code.

  • We’ve fixed a Live-Sync bug, exposed by migration, that prevented us from checking for parent resources when creating relations on external systems. Previously, this caused resources to fail migration if they violated the UniqueConstraintViolatedException transaction condition.

  • The POST applications API faced a latency increase of 170 ms, with response times rising to 380 ms from 220 ms in previous versions. This issue has now been fixed.

  • When a user with limited-role access tries to add a device to a group, it previously resulted in a 500 error. This issue has now been resolved.

  • Previously, attempting to create an organization with a non-existent parentOrgId would result in a 404 error accompanied by an unclear or unhelpful message. This issue has now been fixed, and the system will provide a proper, more informative exception message in such cases.

  • The GET (users/devices/applications)/{id}/permissions endpoint was incorrectly returning duplicate permissions in its response. This issue has now been fixed, and the endpoint will provide a clean, de-duplicated list of permissions.

  • We’ve also addressed a couple of bugs related to validation messages and refactored the migration relationships for improved accuracy and clarity.

  • We’ve resolved an issue where fetching a user’s accounts would previously result in a 400 error if an account ID was encountered in a string format. The system now processes these requests, displaying valid account details and gracefully skipping any account IDs that are incorrectly formatted as strings.