You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing the Owner of an Application feature[1] is not working as expected. When we changed the owner of an application and delete the previous owner, the application key will not display in the Deportal UI. After that, we are not even allowed to re-generate new application keys. When we try to regenerate the Client Credentials it prints a set of ERRORs and will not allow us to regenerate.
[2022-11-10 16:35:28,122] ERROR - AbstractKeyManager Cannot retrieve service provider for the given consumer key : IQm8nWpkLiThVNV0afZSkJgSLmIa
org.wso2.carbon.apimgt.impl.kmclient.KeyManagerClientException: Received status code: 403 Reason:
at org.wso2.carbon.apimgt.impl.kmclient.KMClientErrorDecoder.decode_aroundBody0(KMClientErrorDecoder.java:29) ~[org.wso2.carbon.apimgt.impl_9.0.174.245.jar:?]
at org.wso2.carbon.apimgt.impl.kmclient.KMClientErrorDecoder.decode(KMClientErrorDecoder.java:27) ~[org.wso2.carbon.apimgt.impl_9.0.174.245.jar:?]
at feign.AsyncResponseHandler.handleResponse(AsyncResponseHandler.java:96) ~[io.github.openfeign.feign-core_11.0.0.jar:?]
Description
Changing the Owner of an Application feature[1] is not working as expected. When we changed the owner of an application and delete the previous owner, the application key will not display in the Deportal UI. After that, we are not even allowed to re-generate new application keys. When we try to regenerate the Client Credentials it prints a set of ERRORs and will not allow us to regenerate.
[1] - https://apim.docs.wso2.com/en/4.0.0/consume/manage-application/advanced-topics/changing-the-owner-of-an-application/
Steps to Reproduce
Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: