Upgrading

The AnyCAGateway REST is compatible with Keyfactor Command version 11 and above. Previous Keyfactor AnyCAGateway DCOM versions 20.7 and above can be upgraded to the AnyCAGateway REST.

Note:  If you’re upgrading from an instance of the AnyCAGateway DCOM, the upgrade of the database must be run on the existing Anygateway server, or a server that is domain-joined with the existing Anygateway server. However, once the database is upgraded, the new AnyCAGateway REST can be installed anywhere.
Note:  The Extensions folder is preserved during upgrades. All existing extensions and files located in the install destination's Extensions folder will be preserved unless a file or folder with the same name exists in the Extensions folder located at the source. By default, the Extensions folder (for previous version) is located at:

C:\Program Files\Keyfactor\Keyfactor AnyCA Gateway\AnyGatewayREST\net6.0\Extensions

This can be useful behavior to invoke, especially with regard to the manifest.json file, ensuring the older version of the file no longer exists after an upgrade to prevent unintended behaviors, when the manifest.json file from the source will overwrite the existing manifest.json file at the destination. This can be useful for upgrading an existing extension without going into the install location and manually deleting/modifying the files.

Note:  Migrations from installations on Windows to installations in containers under Kubernetes with an upgrade are only supported from an existing AnyCAGateway REST implementation. If you’re starting with an instance of the AnyCAGateway DCOM, upgraded to an instance of the AnyCAGateway REST on Windows before migrating to a container implementation.
AnyCA Gateway Upgrade Compatibility Matrix

There are two formats of the AnyCA Gateway—DCOM and REST. While it is the intention to deprecate the DCOM format eventually, for a brief period, both versions will be released. This complicates the upgrade process, in terms of determining whether a given gateway install can or cannot be upgraded to a particular destination version.

The rules as to what upgrades are allowed are as follows:

  • Upgrading from an older DCOM gateway to a newer DCOM gateway is allowed.

  • Upgrading from an older REST gateway to a newer REST gateway is allowed.

  • Converting a DCOM gateway to a REST gateway is only allowed on the exact version (so 24.1 DCOM can upgrade directly to 24.1 REST, but 23.4 DCOM cannot).

  • Converting from a REST gateway to a DCOM gateway is never allowed.

See Table 984: AnyCA Gateway Upgrade Compatibility Matrix for upgrade compatibility between AnyCA Gateway formats.

Table 984: AnyCA Gateway Upgrade Compatibility Matrix

Source Version → From

Target Version ↓ To

 DCOM v22.1.1 DCOM v23.3 DCOM v23.4 DCOM v24.1 DCOM v24.2 DCOM v24.3 REST v23.1 REST v24.1 REST v24.2 REST v24.3 REST v24.4
DCOM v22.1.1  
DCOM v23.3  
DCOM v23.4  
DCOM v24.1  
DCOM v24.2  
DCOM v24.3  
REST v23.1 * * + + +  
REST v24.1 * * * + +  
REST v24.2 # # # # +  
REST v24.3 # # # # #  
REST v24.4 # # # # #  

Table 985: Legend: AnyCA Gateway Upgrade Compatibility Matrix

Symbol Meaning
Supported

Downgrade not supported, or REST to DCOM not supported
* Not Supported - Must upgrade to DCOM 24.1, then to REST v24.1
# Not Supported - Must upgrade to the supported DCOM version on this row, then to the REST version
+ Not Supported - Must upgrade directly to the supported REST version in this column
  Same Version
  Supported - Special case - This was the most recent DCOM release at the time of the REST 23.1 release