Skip to content
Identity and Access Management

22 September 2025

Production release: 22 September 2025
Staging release: 16 September 2025

22 September 2025

Section titled “22 September 2025”

Enhancements

Section titled “Enhancements”

  • Subgroup name uniqueness check in parent group: Subgroup names must now be unique only within their parent group, not across the entire account.

  • Roleless Users - View Access: Users who are added to the group without an assigned role should have permission to view other users.

  • Multi-Owner Support Enabled: The IAM system currently restricts each account to a single Account Owner, limiting management flexibility. To address current requirements, we will temporarily permit multiple Account Owners, controlled by a feature flag. This constraint will be reinstated in the future.

  • FileService Lambda for DataOps: A Lambda function has been developed to upload files from S3 to FileService storage, facilitating analytics data processing by the DataOps team.

  • Bulk Fetch from Multiple Tables: Bulk fetch for multiple entities previously retrieved all data from the regional table only. With some entities now moved to the central table, this function has been updated to support fetching from both regional and central tables.

  • Upgraded TAM Appliance to latest version: The latest version of TAM appliance has been applied in IAM & ApiCloud, ensuring up-to-date functionality and security.

  • Handle Common Error Code in Organization/Group BLU: Organization BLU and Group methods now handle common error codes, improving error management and consistency.

  • Implement Error Codes in Accounts BLU: Error codes have been implemented in Accounts BLU, ensuring unique error identification and documentation.

  • List Users of the Customer Account API supports role IDs: List users of the customer accounts api will return the role IDs to distinguish between owner and admin users. This enhancement also prepares the API for future support of additional user types.

  • Committed status persistence: When a group is created using a user or application token, the relation between the creator and the group is now automatically persisted with the status field set to COMMITTED. This ensures consistency with the consent workflow, where the group owner’s relation is always marked as committed upon creation.

Bugfix

Section titled “Bugfix”

  • List more than 20 subgroups in parent group: Resolved an issue that caused a server error when querying more than 20 group IDs. The API now correctly handles requests with over 20 group IDs.

  • Unhandled Exception in Regional Events Handler Lambda: Resolved an unhandled exception in the Regional Events Handler Lambda that occurred when processing unknown event type references.

  • Sonar fixes: Fixed major issues in Bootstrap BLU, Device BLU, and the common layer.

  • User email addresses are now saved in lower case to match TID storage standards.

  • Non-Dealer Can Manage Organizations Without Permission: Resolved an issue allowing non-dealer users to manage organizations without required permissions.

  • Issues with the /invitation Endpoint: Resolved issues with the invitation endpoint, including incorrect default field settings and rollback failures.

  • New User Invitations Propagated as Existing Invitations: Resolved an issue where new user invitations were incorrectly processed as existing invitations.

  • Accounts Search by Name and Country Produces Additional Accounts: Enhanced account search by name and country to return only exact name matches, minimizing unrelated results.

  • Improper Input Validation in Device Search API: Improved input validation in the Device Search API to ensure responses are returned only for valid field combinations.

  • Able to Create a Preferred Device with Whitespace Characters: Restricted device creation to prevent mandatory fields from containing only whitespace characters.