Welcome to our docs site. Docs on this site are for ACP version 9.
See these links for previous versions: Version 8, Version 7

Release Notes for Apprenda 7.1.x

The following are release notes for the latest version of the Apprenda Cloud Platform.


Release Date: July 18, 2017

Bug Fixes

  • Guest applications that were utilizing Vanity URLs were all improperly running as the “catch-all” application pool identity rather than unique identities. This issue affects versions 6.8.0, 7.0.0, and 7.1.0 and has been resolved in Platform version 7.1.1


Release Date: June 29, 2017

Minor Features/Improvements

  • The Platform is now enabled to use Virtual Accounts as the default for managing and running guest application WCF and Windows Services. Virtual Accounts is a Windows Server feature that will automatically create a different user for a deployed workload, allowing for increased isolation for workloads running on the Platform and reducing operational overhead for managing domain service accounts.

  • Improvements have been made to the Platform’s WCF Services capabilities to allow Developer to configure some custom behaviors for their WCF Services guest applications.

  • Developers can now specify environment variables for their applications through the Developer Portal

  • Improvements were made to how Developers can manage subscription assignment for multi-Tenant applications. The ability to manage subscriptions is now controlled by the Manage Users and Subscriptions securable and these actions can be automated by using new endpoints in the Application Management API

Bug Fixes

Apprenda Installer & Upgrade

  • Modifying an existing Platform to add a new cloud using the Apprenda Installer Wizard would error out because the Platform was not pre-fetching needed information before trying to update redirect rules for the new Cloud.
  • In some cases, when a Platform Coordination node had multiple IP addresses, the ZooKeeper service on the node could become unhealthy leading to installation failures. The configuration of ZooKeeper service to bind to all IPs for a given machine has been improved to resolve this issue.
  • Added a Log Mask created at installation or upgrade time to mask passwords logged by a third party component in certain circumstances


  • Screening to URL forwarding addresses has been added to the Platform’s Maintenance page
  • Email auto-completion was suggesting email addresses for users from other Tenants when creating a new user for a Tenant. Auto-completion feature was removed from the email field of the Create User section of the Users page in the Account Portal
  • Fixed an issue that prevented usage of component specific user accounts for .NET User Interface components.

Developer Portal and Tools

  • When throttling was enabled and no default policy was assigned, application components were incorrectly displaying that a policy had been assigned on an application’s Scale Policies page
  • Removed “Full patching functionality is not yet available in this release” warning message that was no longer applicable on the Patching page

System Operations Center

  • The Platform was incorrectly escaping default values selected while editing a Custom Property
  • Fixed the wrapping text that caused a scrollbar to incorrectly appear on the Add-Ons page
  • Incorrect text wrapping caused misaligned labels on the database node details section on a Database overview page
  • Active link highlighting was incorrectly being removed when navigating two or more pages deep into a section of the SOC
  • Column header on the Tenant page was being to be cut off due to an incorrect width of the Users column
  • Fixed localization issue that caused some pages in the SOC to not display when trying to view it from certain locations
  • Tooltip icons were being displayed incorrectly on the Create Tenant page
  • Fixed a routing issue between multiple clouds that prevented updates to Front End SSL certificates through the SOC

Guest Application Creation and Management

  • Scheduled scaling settings in the Developer Portal were treating blank values as 0 desired instances of an application component. This has been updated so if no value has been entered for a schedule time, the Platform will use the value from the previous day and time as the desired instance count. Developers will now need to explicitly place 0 into a scheduled time to schedule 0 instances of an application component.
  • Changes made to the Pipeline Mode setting of a .NET User Interface component were not being properly applied when the component was deployed to the Platform


  • Fixed issue exposing the IMetadataExchange endpoint for WCF service components when internal traffic encryption was enabled