Hello,
I am migrating the signing configuration from a SafeNet/eToken certificate to a new Sectigo EV code-signing certificate on a YubiKey. I need guidance on the officially supported way to make this work without interactive PIN prompts while preserving Advanced Installer’s native batch signing.
Environment
Advanced Installer: 21.1
Build machine: Windows x64
Token: YubiKey 5 NFC FIPS
Firmware: 5.7.4
PIV FIPS approved: True
Private key: ECC P-256, generated on the YubiKey
PIV slot: 9A
Certificate subject: ROMICO GmbH
Certificate issuer: Sectigo Public Code Signing CA EV E36
YubiKey Smart Card Minidriver: installed
Windows key provider: Microsoft Smart Card Key Storage Provider
Certificate store: Current User\Personal
HasPrivateKey: True
Previous working configuration:
With the SafeNet/eToken certificate, I used:
Sign Tool: Built-in
Certificate source: Use file from disk
Cryptographic service provider: eToken Base Cryptographic Provider
Private key container: the corresponding token key container
Password: automatically — store encrypted password in project file
I need an equivalent unattended workflow for the new YubiKey certificate.
Current problems
With Built-in signing and the YubiKey certificate selected through Use from certificate store, I still need to enter the token PIN interactively. I have not found a supported setting for supplying the YubiKey PIN automatically.
I also use the following registry setting:
HKEY_CURRENT_USER\Software\Caphyon\Advanced Installer\Settings
UseBatchSigning
Type: REG_DWORD
Value: 1
However, when switching to Sign Tool → Custom, this setting does not produce batch signing in my tests. Therefore, switching to a custom signing command is not an equivalent replacement for the existing workflow: even if the external tool can accept the PIN non-interactively, the native batch-signing behavior is lost.
Required result:
I need normal .aip builds to run completely unattended, using the existing certificate and private key on the YubiKey, while retaining native batch signing.
Zero interactive PIN prompts are required. Reducing the number of prompts, or requiring one manual PIN entry before each build/session, does not meet this requirement.
My preferred configuration would retain the equivalent of Use file from disk with an encrypted credential stored in the project. If that is not supported for YubiKey, please specify the supported way to provide the PIN securely and non-interactively during the build.
Questions
1. Does Advanced Installer 21.1 support unattended YubiKey ECC signing with native UseBatchSigning?
If so, please provide the exact configuration, including the certificate source, provider/container settings where applicable, and the supported PIN-supply mechanism.
2. Is UseBatchSigning intentionally unsupported or ignored when Sign Tool → Custom is selected?
Is there another supported setting or interface that passes multiple files to the custom signing tool in one invocation?
3. Does a newer Advanced Installer version support this combination?
If so, please identify the minimum version and the relevant feature or fix, together with configuration instructions.
4. If this combination is not supported, please confirm the limitation explicitly.
If this scenario is not supported, please let me know whether the limitation is on the Advanced Installer side or comes from the signing provider / YubiKey integration.
I would also like to know whether there is an officially supported solution, rather than a workaround based on custom Build Events.
My goal is to keep the signing process integrated into the normal .aip build workflow, the same way it currently works with the SafeNet token.
I understand that batch signing can still involve separate signing stages for application files and the resulting installer components. I do not require a single signing invocation for the entire build; I need to retain the existing grouping of files without having to enter the PIN manually.
Best regards
Pawel
FOLLOW US
Get the latest news in Application Packaging