[SELC-9178] IAM: Removed productId, tenantId from ProductRolePermissionsList

[gaetano-miglionico]

This pull request introduces support for a new tenantId parameter across the IAM API documentation, backend service logic, and related tests. The main focus is to make the tenantId available in API requests and ensure it is consistently passed through service layers and tested throughout the codebase.

API Documentation Updates:

• Added a tenantId field to relevant request and response schemas in both api-iam-docs.json and api-docs.json, ensuring the OpenAPI specs reflect the new parameter. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

• Updated endpoint definitions to accept tenantId as an optional query parameter, with a default value of "AR". [1] [2] [3] [4] [5] [6] [7]

Backend Service Changes:

• Modified all calls to iamExternalRestClient._getIAMProductRolePermissionsList and iamRestClient._hasIAMUserPermission to include the tenantId parameter, defaulting to "AR". This ensures tenant context is always passed to IAM permission checks and role queries. [1] [2] [3] [4] [5] [6]

Testing Updates:

• Updated unit tests to include the tenantId parameter in all relevant mock and verification calls, ensuring test coverage for the new logic. [1] [2] [3] [4] [5] [6] [7] [8]

Other Minor Changes:

• Minor property order and formatting adjustments in the OpenAPI JSON files for consistency. [1] [2] [3] [4]
• Removed an unused import in ExchangeTokenServiceV2.java.

---

Summary of Most Important Changes:

API Schema and Endpoint Enhancements:

• Added tenantId as a property and query parameter in relevant OpenAPI schemas and endpoints, with a default value of "AR". [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Backend Service Logic:

• Updated all service and client calls to IAM permission and role APIs to include the new tenantId parameter, ensuring tenant-aware authorization logic. [1] [2] [3] [4] [5] [6]

Testing:

• Modified and extended test cases to mock and verify the new tenantId parameter in all relevant IAM client calls. [1] [2] [3] [4] [5] [6] [7] [8]

Code Cleanup:

• Removed an unused import from ExchangeTokenServiceV2.java.

Schema Consistency:

• Adjusted property order and formatting in OpenAPI files for consistency and clarity. [1] [2] [3] [4]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud