Feature Request
Motivation Behind Feature
To improve security and simplify the build workflow, it is essential to integrate support for Azure Trusted Signing into cordova-electron. Since electron-builder already supports this feature, cordova-electron should simply pass the configuration options to electron-builder. This will allow developers to easily enable Azure signing without having to manage additional configurations or external scripts
Feature Description
The goal is to add a new configuration section in build.json, for example azureSignOptions, which will be recognized by cordova-electron and passed directly to electron-builder during the build process. The proposed configuration is as follows:
{
"electron": {
"windows": {
"azureSignOptions": {
"endpoint": "<Trusted Signing account endpoint>",
"publisherName": "<Publisher name>",
"certificateProfileName": "<Certificate profile name>",
"codeSigningAccountName": "<Trusted Signing account name>"
}
}
}
}The expected behavior is as follows:
Configuration Retrieval: Cordova-electron should read the azureSignOptions present in the configuration file (e.g., build.json).
Transmission to electron-builder: These options should be passed to electron-builder, which will then use these parameters to sign the application via Azure Trusted Signing.
Alternatives or Workarounds
Currently, developers must either manually modify electron-builder’s configuration or use external scripts to integrate Azure Trusted Signing after the build. This approach increases complexity and the risk of errors. By centralizing this configuration in cordova-electron and automatically passing it to electron-builder, the process becomes simpler and less error-prone, providing a better user experience.
Feature Request
Motivation Behind Feature
To improve security and simplify the build workflow, it is essential to integrate support for Azure Trusted Signing into cordova-electron. Since electron-builder already supports this feature, cordova-electron should simply pass the configuration options to electron-builder. This will allow developers to easily enable Azure signing without having to manage additional configurations or external scripts
Feature Description
The goal is to add a new configuration section in build.json, for example azureSignOptions, which will be recognized by cordova-electron and passed directly to electron-builder during the build process. The proposed configuration is as follows:
{ "electron": { "windows": { "azureSignOptions": { "endpoint": "<Trusted Signing account endpoint>", "publisherName": "<Publisher name>", "certificateProfileName": "<Certificate profile name>", "codeSigningAccountName": "<Trusted Signing account name>" } } } }The expected behavior is as follows:
Configuration Retrieval: Cordova-electron should read the azureSignOptions present in the configuration file (e.g., build.json).
Transmission to electron-builder: These options should be passed to electron-builder, which will then use these parameters to sign the application via Azure Trusted Signing.
Alternatives or Workarounds
Currently, developers must either manually modify electron-builder’s configuration or use external scripts to integrate Azure Trusted Signing after the build. This approach increases complexity and the risk of errors. By centralizing this configuration in cordova-electron and automatically passing it to electron-builder, the process becomes simpler and less error-prone, providing a better user experience.