We currently predefine a set of signing drivers (those that reside in the repository are prepackaged) for the Wallet Gateway.
Instead, the Wallet Gateway artifact should support a configuration that allows en-/disabling pre-packaged signing drivers, as well as invoking signing drivers from an external package. E.g. a plug-in like experience.
If the approach with the artifact is inconvenient for some reason, one could also explore the option in which the WG itself is a dependency of a custom-WG project that includes different signing drivers.
We currently predefine a set of signing drivers (those that reside in the repository are prepackaged) for the Wallet Gateway.
Instead, the Wallet Gateway artifact should support a configuration that allows en-/disabling pre-packaged signing drivers, as well as invoking signing drivers from an external package. E.g. a plug-in like experience.
If the approach with the artifact is inconvenient for some reason, one could also explore the option in which the WG itself is a dependency of a custom-WG project that includes different signing drivers.