In some scenarios, you may need to support two versions of the same certificate store extension. A common example is the F5 Orchestrator, where you may need to maintain compatibility with F5 v13, which requires extension version 1.6 or lower.
Key considerations
Multiple versions on a single Universal Orchestrator (UO)
You cannot install two versions of the same orchestrator extension on a single Universal Orchestrator. However, you can install multiple Universal Orchestrators on the same server. Each UO can host a different version of the extension.
Certificate store type definitions (schema)
If two versions of the extension define different certificate store type schemas, they cannot be supported—even if installed on different UOs. This is because Command does not version certificate store types.
In some extension updates, the certificate store type definition changes, which can cause compatibility issues.
Using alternate capability names
It is technically possible to work around schema conflicts by assigning alternate capability names for one of the versions. However, this approach complicates deployment and should only be considered if absolutely necessary.
Enabling multiple versions in Command
To run multiple versions of a certificate store type at the same time, you can create a second copy of the certificate store type definition in Command, giving it a unique name. Each orchestrator extension version must then be registered in the manifest with the corresponding name in Command.
Technical limitation
Two versions of the same extension cannot be loaded into a single UO installation. This is because the manifest maps the certificate store type (capability name) to a unique .NET assembly (DLL), and the assembly names remain unchanged across versions. Therefore, to run two versions concurrently, you must install separate UOs, each running as an independent service. These services may run on the same server but must remain isolated.
Comments
Please sign in to leave a comment.