[APIM 4.1.0] Unable to view the Application Consumer Key and Secret

[Hamool-Nizar]

Description

We are migrated to the APIM 4.1.0 from the APIM 3.1.0 along with iS as KM (5.10.0 to 5.11.0). After the migration, we are unable to view the Application consumer key and secret in the Devportal as follows

After further investigating this issue, we identified that trying to view the consumer keys and secret for the super admin’s applications within the other tenants Devportal UI is not possible in the current APIM 4.1.0. Hence the above issue is expected in the APIM 4.1.0, and we cannot view the Application consumer key and secret for the applications created within other than itself. If we want to view the Application consumer key and secret then we have to switch to the correct tenant and then we can view the consumer key and secret.

But the same cross-tenant subscription behaviour in different from our current APIM 3.1.0, where in the current APIM 3.1.0 we were able to follow the same steps in our current APIM 3.1.0 environment and we were able to view the Application consumer key and secret in the Devportal.

Therefore, could you please confirm which of the APIM 3.1.0/4.1.0 behaviour is the expected and acceptable behaviour in the APIM products. Additionally, if the we want to replicate the same behaviour in the latest APIM 4.1.0, could you please share inputs/suggestions on how we can achieve this requirement.

Best regards,
Hamool

Steps to Reproduce

1. Log into the Devportal using the super admin credentials.
2. Create an application in the super tenant (carbon.super).
3. Subscribe to one/more APIs in the super tenant using the new application
4. Generate tokens in the newly created application.
5. Then switch to another tenant in the Devportal using the “SWITCH DEV PORTALS” option.
6. List the applications and select the newly created application.
7. Go to the Production Keys to view the consumer key and secret.
8. Then you should be able to get the following result respectively in APIM 3.1.0 and APIM 4.1.0.

- APIM 3.1.0

- APIM 4.1.0

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

[hisanhunais]

The fix for this issue has been delivered via an update for APIM 4.1.0 and the fix is available in the public branch as well. The issue can be solved via the Global Key Manager [1] which was provided as the fix.

[1] https://apim.docs.wso2.com/en/4.1.0/administer/key-managers/configure-global-key-manager/#configure-the-global-key-manager