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 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
Create a gateway using deployment.toml by following the official WSO2 documentation:
Navigate to Admin Portal → Gateways through the left menu.
Select the gateway created via deployment.toml and click on the Edit icon.
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."
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
The text was updated successfully, but these errors were encountered:
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
deployment.toml
by following the official WSO2 documentation:deployment.toml
and click on the Edit icon.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
The text was updated successfully, but these errors were encountered: