Adaptiv Cloud Orchestrator v4.3

This page list all the releases for Adaptiv Cloud Orchestrator v4.3.0.

Release 4.3.0

Release Date: March 13, 2026

Features and Enhancements

Firewall Policy Override – The release introduces a new policy override feature in firewall policies. This feature enables customers to create ALLOW policies that take priority over broader BLOCK rules. With this capability, customers can permit specific types of traffic even when a general block is in place for that category. The override ALLOW rule will always take precedence, ensuring that the critical traffic flows without interruption while the wider security policy remains intact. Please note that this feature requires the CPE to run on AOS v8.4.0 or greater. For functionality details, see Override Policy.
Security fixes and improvements – We continue the improve overall orchestrator security by addressing vulnerabilities and adding security fixes.

Caveats

It is recommended that My Connect licenses be created and deployed using a single service order.
To apply changes to My Connect users, resources, or private subnet configuration, the Update button from My Connect dashboard must be clicked every time.
Changing device type for a site with traffic steering custom site configuration may result in the custom site configuration not being correctly applied to the site. If a device change is necessary, we advise deleting the current site and creating a new one with new custom configuration.
The network quality steering feature listed under device configuration in service orders cannot be implemented on the customer sites and is available for demo purposes (demo sites) only.

Open Issues

1086 – In service orders, users cannot create a customer whose name contains a substring that is already used in an existing customer name.
1462 – The Data Center value for static IP block cannot be modified for service orders with static IP at LAN. To change the Data Center value, remove the site from the queue, and edit it to set the static IP configuration to none. Save the site and edit again to choose the static IP at LAN configuration with the required data center.
1556 – If a user did not receive a recovery code during the multifactor authentication (MFA) setup process, multifactor login will not display the recovery code when they choose to "try another method" when they log in with MFA the next time. In this case, please contact Adaptiv Networks to reset the MFA account for the user. Examples of not receiving recovery code include browser being killed during the setup process or user did not select the "I have safely recorded this code" checkbox.
1561 – The "Forgot Password" login screen allows you to enter an email address other than their own. Adaptiv Networks recommends not editing the email address when trying to reset the password.
1586 – For a site with active DHCP reservations, routable subnets, or IP rules, a user cannot use a service order to modify the static public IP configuration. In this case, the site needs to be deleted and redeployed in order to modify the static public IP configuration.
1633 – A WAN port that has been configured through device management but has not yet been deployed is displayed as High rather than Not in Use. In order to see the port's correct status, the configuration needs to be deployed.
1676 – A user is prompted to enter the verification code rather than their login credentials after being logged out of the orchestrator and My Connect client due to inactivity.
1744 – An orchestrator user is prompted to reset their password in order to access the My Connect client after being invited to join Adaptiv My Connect. They can, however, continue to log in to the My Connect client using the same orchestrator password.
1748 – When a user is forced to reset their password for My Connect client or Adaptiv Cloud Orchestrator, the user is not logged out of the application. However, the user is required to change their password before logging back to My Connect client or Adaptiv Cloud Orchestrator.
1773 – Sometimes the customer pin on the map in partner dashboard is misplaced after changing customer address.
1775 – On My Connect dashboard, when there is an orchestrator user with My Connect access, the orchestrator is greyed out in the list of resources in the Manage Resources form. To enable the orchestrator resource for the other users, either remove the ACO user with AMC access from the list or enable it for each individual user.
1820 – When using the mobile phone view in the Safari browser, the user profile view does not function as expected.
1837 – Customers who have multiple service orders may occasionally still see a pin on the partner dashboard's map even if they do not have any sites or My Connect licenses deployed.
1890 – In a service order containing only deployed My Connect licenses, if the licenses are removed and a site is added, the service order remains in In Progress status rather than going for completion.
1984 – When the customer address is updated in an existing service order and a site from that order is added to the deployment queue, the site summary does not reflect the updated address.
2006 – The dashboard maps may occasionally show regions with a note saying "sorry, we have no image here." Refreshing the browser will display the map with all regions.
2022 – In service orders, editing a site to change the device type results in Traffic Steering template drop-down on Technical Configuration page being blank. A browser refresh will load the template in drop-down.
2050 – In certain failure scenarios within an HA deployment, the site dashboard may inaccurately display Active/Inactive status of the primary and secondary device. While the traffic continues to flow correctly, the status of device might be incorrect. In such cases, you can use Remote Access to connect to the device’s GUI and verify its HA status.
2267 – The service order table does not update the status of order from "Complete" to "In Progress" after all the sites from that order are deleted and the "Delete" button in the service order table remains disabled as well. A browser refresh is required to reflect the updated status.
2295 – In My Connect bulk user import, sometimes, the cancel import operation might appear to fail because the bulk import operation is completed before the cancel request is processed.
2331 – For customers with a large number of deployed sites, reducing the map size on the customer dashboard may cause the map to display fewer site pins than the actual number of deployed sites.
2356 – When editing a site, removed from purchase queue, a flickering red error message briefly appears in the Edit Site form.
2357 – When configuring a Virtual Edge using LAN port 1 (default) with an IP@LAN address, the Site Summary page does not display the LAN port information.