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
Describe the bug
The hasync_hosts, hasync_username and hasync_password fields are not being set during PUT requests to /api/v1/system/api. This is because the field validation is not using isset($this->validated_data["hasync"]) to trigger the logic and is instead using $this->validated_data["hasync"] which never triggers because pfSense stores the value as an empty string.
Expected behavior
Whenever hasync is set to true, the hasync_hosts, hasync_username and hasync_password fields should become required. Instead, they are being skipped entirely.
pfSense Version & Package Version:
pfSense Version: All
Package Version v1.5.0 and earlier
Affected Endpoints:
/api/v1/system/api
The text was updated successfully, but these errors were encountered:
Describe the bug
The
hasync_hosts
,hasync_username
andhasync_password
fields are not being set during PUT requests to /api/v1/system/api. This is because the field validation is not usingisset($this->validated_data["hasync"])
to trigger the logic and is instead using$this->validated_data["hasync"]
which never triggers because pfSense stores the value as an empty string.To Reproduce
Expected behavior
Whenever
hasync
is set totrue
, thehasync_hosts
,hasync_username
andhasync_password
fields should become required. Instead, they are being skipped entirely.pfSense Version & Package Version:
Affected Endpoints:
The text was updated successfully, but these errors were encountered: