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
When changing the Provider of an API from the WSO2 API Manager Admin Portal, multiple issues can be observed;
The provider name can be saved as user @carbon.super (with a space before @), which is incorrect.
If the provider name is not edited and saved after clicking on the edit button, an error occurs stating "API provider should not be empty", even when a valid provider is present.
If the Edit button is clicked on one API, then the Edit button of the provider name on another API is clicked, and the provider of the second API is modified, clicking Save on the first API incorrectly replaces the provider name of the first API with the edited name of the second one.
Entering an invalid provider name format, such as user@carbon .super (with a space after @) or an invalid tenant, results in a java.lang.NullPointerException from the backend.
Steps to Reproduce
Open the Admin Portal and navigate to Change API Provider under Settings.
Click Edit and modify the Provider field.
Try entering provider names with incorrect spaces (e.g., user @carbon.super or user@carbon .super).
Edit the provider of one API, then switch to another API, edit its provider, and save the first API.
Observe the error messages or incorrect provider replacements.
Screen.Recording.2025-02-27.at.16.48.20.mov
Version
4.5.0-beta
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered:
Description
When changing the Provider of an API from the WSO2 API Manager Admin Portal, multiple issues can be observed;
user @carbon.super
(with a space before@
), which is incorrect.user@carbon .super
(with a space after @) or an invalid tenant, results in ajava.lang.NullPointerException
from the backend.Steps to Reproduce
Change API Provider
under Settings.user @carbon.super
oruser@carbon .super
).Screen.Recording.2025-02-27.at.16.48.20.mov
Version
4.5.0-beta
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered: