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
We use the module Module fmgr_fwobj_address
this module works properly before the upgrade, it sends to fortimanager the visibility parameter
{
"method": "add",
"params": [
{
"url": "/pm/config/adom/DATA4/obj/firewall/address",
"data": {
"comment": "Created by no body",
"associated-interface": null,
"cache-ttl": null,
"name": "ARFARFARF",
"allow-routing": "disable",
"color": "22",
"meta fields": {},
"dynamic_mapping": [],
"visibility": "disable",
"type": "ipmask",
"subnet": [
"192.168.254.0",
"255.255.255.0"
]
}
}
],
"session": "AbigString",
"id": 4,
"verbose": 1
}
Since the fortimanger upgrade 6.4.8 -> 6.4.10 this parameter causes the folowing fault
"status": {
"code": -10,
"message": "The data is invalid for selected url"
},
The text was updated successfully, but these errors were encountered:
Thank you for raising this issue, It seems like the latest FMG API has remove this argument from database, so the system can't recognize "visibility", My suggestion is removing this argument from data, I will ask FMG API team if that is on purpose.
We use the module Module fmgr_fwobj_address
this module works properly before the upgrade, it sends to fortimanager the visibility parameter
{
"method": "add",
"params": [
{
"url": "/pm/config/adom/DATA4/obj/firewall/address",
"data": {
"comment": "Created by no body",
"associated-interface": null,
"cache-ttl": null,
"name": "ARFARFARF",
"allow-routing": "disable",
"color": "22",
"meta fields": {},
"dynamic_mapping": [],
"visibility": "disable",
"type": "ipmask",
"subnet": [
"192.168.254.0",
"255.255.255.0"
]
}
}
],
"session": "AbigString",
"id": 4,
"verbose": 1
}
Since the fortimanger upgrade 6.4.8 -> 6.4.10 this parameter causes the folowing fault
"status": {
"code": -10,
"message": "The data is invalid for selected url"
},
The text was updated successfully, but these errors were encountered: