Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Admin Portal] Issues When Changing API Provider in Admin Portal #3735

Open
AqeelMuhammad opened this issue Feb 27, 2025 · 0 comments
Open

Comments

@AqeelMuhammad
Copy link

Description

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.
Image

Steps to Reproduce

  1. Open the Admin Portal and navigate to Change API Provider under Settings.
  2. Click Edit and modify the Provider field.
  3. Try entering provider names with incorrect spaces (e.g., user @carbon.super or user@carbon .super).
  4. Edit the provider of one API, then switch to another API, edit its provider, and save the first API.
  5. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants