-
Prasad Neelapala
- PowerBuilder
- Thursday, 5 February 2026 01:48 PM UTC
Hi Team,
I am reaching out regarding the certificate (Launch_key.pfx) used to sign the ClickOnce deployment package for our application. The certificate is set to expire in 20 days, and I would like your advice on the potential impact this may have on the application and future deployments. Specifically, I would like clarification on the following points:
Will the expiration of the certificate affect the functionality of the currently installed application for end users?
Will it impact the ability to deploy updates or new versions of the application after the certificate expires?
Are there any recommended steps we should take to renew or replace the certificate to ensure seamless future deployments?
Additionally, the current signing process includes a timestamp URI (http://timestamp.digicert.com) to ensure the validity of the signature. Please confirm if this mitigates any risks associated with the certificate expiration.
current code where we use the pfx file in clickonce.bat
set PFX_PATH=%~dp0Launch_key.pfx
set PFX_FILE=%PFX_PATH%
echo Signing Launch.exe.manifest with SHA-256 algorithm and Timestamp...
%MAGE_PATH% -Sign %l_dir%\Launch.exe.manifest -CertFile %PFX_FILE% -Password %PFX_PASSWORD% -Algorithm sha256 -TimeStampUri %TIMESTAMP_URL%
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.