Product Updates

FWD-29801 Support managing API key credentials in the UIThe release 23.1 allows the user to manage, directly in the UI, the API key credentials needed to enable the Collector to log in to devices that require an API key.  

Topology​FWD-29297 Remove synthetic device editing from location toolbar Release 22.11 had already placed the managing of the synthetic devices at pair with the other collection sources. A new tab was in fact added to the Sources page and from there the user can fully manage these critical objects. This additional enhancement completes the transition by removing the synthetic device editing from the location toolbar.Processing​FWD-29506 Improve duplicate device removal This enhancement improves the order of preference when choosing the winner among what appear to be duplicate devices. The logic to verify that two network devices that are discovered by Forward or added by the users are not the same device is quite complex and takes into account several factors. This enhancement further improves the logic for deduplication by implementing the following preferences: Prefer the device that does not use a jump server Prefer the device referenced to with a hostname rather than an IP address Prefer the device with shorter name Modeling​ FWDN-7613 AWS - Support layer 7 features in AWS application load balancer Learn more on the AWS documentation page. FWDN-912 Nokia - Support for additional features on Nokia devices Support for Nokia 7750 and 7700 family was introduced in the 22.12 release. The 23.1 release adds support for additional functionality like ACL filters and EVPN for MPLS in Epipe service. FWDN-7281 ForcePoint - Initial support for ForcePoint Next Gen Firewalls FWDN-7633 Viptela - vSmart collection The collector now places the state files collected for vSmart into each vEdge snapshot for modeling. FWDN-7663 Privilege mode password association with login credentials This enhancement implements a logic that allows for retries when a privilege mode error occurs. When this happens, the system will now also try the other available credentials, until one of them passes the privilege password discovery part. If none of them passes, then the system reports the failure as a privilege password issue.