Adaptiv Cloud Orchestrator v4.5

This page lists all the releases for Adaptiv Cloud Orchestrator v4.5.0.

Release Date: July 31, 2026

Features and Enhancements

Sign in with Single Sign-On (SSO) using Google or Microsoft workspace – ACO users can now sign in to the Orchestrator using Single Sign-On (SSO) with their Google or Microsoft Workspace email address. Available to both new and existing users, SSO simplifies the login process while enhancing account security by eliminating the need to manage separate passwords. Standard email and password login remains available, though we strongly recommend switching to SSO for a faster, more secure experience. For details, see Sign In and Multifactor Authentication.

Automatic blocking of Unknown category in security templates – To safeguard your network against unverified web risks, release 4.5.0 automatically blocks the Unknown traffic category across the Very Light, Light, and Standard policy templates. With the exception of No Filter template, all other templates under Web URL Filtering under Web Protect will block the Unknown category traffic. This change actively safeguards your network from potential threats associated with unclassified URLs, unverified CDNs, unknown IPs, and web-messaging platforms. For details, see Web Protect Security templates.

Existing customers with sites or My Connect licenses using Very Light, Light, or Standard security templates will see a blue change indicator next to Security in the left-hand menu of Site Management, along with an Update button. Customers must click the Update button to apply the latest template version to their network.

Performance enhancements – System-wide enhancements and performance optimizations for a faster, smoother, and more responsive experience.

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 the My Connect dashboard must be clicked every time.
Changing the device type for a site with traffic steering, a 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 a 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.

Addressed Issues

1086 – In service orders, users cannot create a customer whose name contains a substring that is already used in an existing customer name.
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 to modify the static public IP configuration.
2356 – When editing a site, removed from the 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.
2381– When opening the Site Summary page, the Customer section briefly displays the value “undefined” for a few seconds before populating with the correct customer information. During this time, all other sections of the Site Summary page load and display their data correctly.
2424 – When a user creates a custom site configuration (for app prioritization, traffic steering, and security) from device management and then navigates back to Service Orders, the custom configuration is not immediately displayed under Technical Configuration. A browser refresh is required to see the configuration under Service Orders.

Open Issues

1462 – The Data Center value for the static IP block cannot be modified for service orders with static IP at the 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 the recovery code include the browser being killed during the setup process or the user not selecting the "I have safely recorded this code" checkbox.
1561 – The "Forgot Password" login screen allows you to enter an email address other than your own. Adaptiv Networks recommends not editing the email address when trying to reset the password.
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 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 the 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 the My Connect client or the Adaptiv Cloud Orchestrator.
1773 – Sometimes the customer pin on the map in the partner dashboard is misplaced after changing the 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 the Traffic Steering template drop-down on the Technical Configuration page being blank. A browser refresh will load the template in the drop-down.
2050 – In certain failure scenarios within an HA deployment, the site dashboard may inaccurately display the Active/Inactive status of the primary and secondary devices. While the traffic continues to flow correctly, the status of the 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 the 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.
2415 – Modifying a static public IP reservation fails for sites with a 110 or more character name.
2418 – In Service Orders, occasionally, when an HA site is removed from purchase and the LAN Configuration form is edited, the Primary and Secondary Reserved IP Address field values are not displayed in the form. Closing the form and reopening it in edit mode displays the values.
2419 – In Service Orders, when configuring a site with a Static Public IP at LAN, changing the subnet from /29 to /30 results in the site being incorrectly deployed with a private IP configuration. To deploy the site with correct IP configuration, edit the site to set the static public IP to None and save, then re-edit the site, select static IP at LAN with the correct subnet, and save again to ensure the LAN Configuration displays the public IPs.
2420 – In Service Orders, when a user changes the IP configuration from Static Public IP at LAN to Private IP, the system (orchestrator) allows the user to add the site to the purchase without requiring the necessary private IP details to be configured. As a result, the site is provisioned with an invalid IP address (0.0.0.0). It is, therefore, advised to add the IP details prior to adding the site to purchase.
2427 – In Service Orders, if a user verifies multiple sites that have the same serial number before clicking Save, the system allows the configuration to be saved without validation errors. This results in duplicate serial numbers being assigned across sites.
2428 – In Service Orders > Links Configuration table, clicking Save for a single row silently resets and clears all other modified, unsaved rows across the table. Users are advised to edit and save the configurations one row at a time to prevent loss of progress.
2466 – Deleting a site may cause its routable subnets to remain cached on the front end, resulting in an incorrect subnet overlap error when creating a new site. Refreshing the browser clears the cached data and resolves the error.
2480 – On the customer dashboard, sorting the sites table by certain parameters causes the map view to display fewer site pins than the total number of sites listed in the table. The map fails to render the full set of pins until default sorting is restored.