Save fails with error. Gateway logs show:

TL;DR

The Control UI needs to be updated to exclude the source field from allowlist entries when saving security settings to fix the INVALID_REQUEST error.

Guidance

• Verify the gateway API documentation to confirm the expected properties for allowlist entries, ensuring that source is not a valid field.
• Inspect the Control UI code to identify where the source field is being added to the allowlist entries and modify it to exclude this field.
• Use the provided CLI workaround to set security settings until the UI issue is resolved.
• Test the updated UI by attempting to save security settings and checking the gateway logs for any errors.

Example

No code snippet is provided as the issue does not contain sufficient code details, but the fix would involve modifying the UI code to remove the source field from allowlist entries, for example:

// before
{
  "allowlist": [
    { "command": "...", "glob": "...", "source": "..." },
    ...
  ]
}

// after
{
  "allowlist": [
    { "command": "...", "glob": "..." },
    ...
  ]
}

Notes

The root cause of the issue is the inclusion of the source field in the allowlist entries by the Control UI, which is not accepted by the gateway API. The provided CLI workaround allows security settings to be set correctly until the UI issue is fixed.

Recommendation

Apply the workaround by using the CLI to set security settings until the Control UI is updated to exclude the source field from allowlist entries. This ensures that security settings can be configured correctly while the UI issue is being addressed.