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] [Gateway Configuration] Read-Only Gateway Fields Appear Editable & Update Button is Active #3789

Open
Dakshithas opened this issue Mar 10, 2025 · 0 comments

Comments

@Dakshithas
Copy link

Description

When a gateway is created using the deployment.toml configuration, it should be read-only in the Admin Portal. However, some fields appear editable, and the Update button is active. When users attempt to modify the gateway and click Update, an error message appears stating that the gateway is read-only.

Steps to Reproduce

  1. Create a gateway using deployment.toml by following the official WSO2 documentation:
  2. Navigate to Admin Portal → Gateways through the left menu.
  3. Select the gateway created via deployment.toml and click on the Edit icon.
  4. Observe that:
    • Some fields appear editable, even though the gateway is configured as read-only.
    • The Update button is active, but clicking it results in an error:

      "This gateway is read-only."

Image Image

Expected Behavior

✅ All fields should be disabled (non-editable) for gateways defined in deployment.toml.
✅ The Update button should be disabled to prevent confusion.


Observed Issues

❌ Some fields appear editable, misleading users.
❌ The Update button is active, allowing users to attempt modifications.
❌ Clicking Update results in an error saying the gateway is read-only.


Suggested Fix

🔹 Make all fields non-editable when the gateway is configured via deployment.toml.
🔹 Disable the Update button to prevent users from attempting editing.


Version

APIM 4.5.0 RC2

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