Welcome to the WSO2 Identity Server source code! For info on working with the WSO2 Identity Server repository and contributing code, click the link below.
Describe the issue:
The current implementation exhibits an inconsistency in the format of responses between two distinct endpoints when retrieving API resources.
This issue leads to confusion and challenges in handling API resource details uniformly across different endpoints. The expected behavior is a consistent inclusion of the type attribute in the response format for API resources, ensuring a standardized approach for interpretation and usage.
How to reproduce:
Login to console.
Create an application role and organization role.
Navigate to the permission section of both the application role and organization role.
Observe the network calls for the described scenarios.
Expected behavior:
The type attribute should be consistently included in the response format for API resources across all relevant endpoints, providing a standardized and predictable data structure.
Environment information (Please complete the following information; remove any unnecessary fields) :
PasinduYeshan
commented
10 months ago
Describe the issue: The current implementation exhibits an inconsistency in the format of responses between two distinct endpoints when retrieving API resources.
When fetching API resources from https://localhost:9443/t/carbon.super/api/server/v1/api-resources, the response provides a comprehensive data format, including the type attribute for each API resource.
However, when querying for allowed permissions using https://localhost:9443/t/carbon.super/api/server/v1/applications/{appId}/authorized-apis, the response lacks the type information for the API resources.
This issue leads to confusion and challenges in handling API resource details uniformly across different endpoints. The expected behavior is a consistent inclusion of the type attribute in the response format for API resources, ensuring a standardized approach for interpretation and usage.
How to reproduce:
Expected behavior: The type attribute should be consistently included in the response format for API resources across all relevant endpoints, providing a standardized and predictable data structure.
Environment information (Please complete the following information; remove any unnecessary fields) :
Optional Fields
Related issues:
Suggested labels: