Inspirometer Developer
Posts: 34
Joined: 2017-10-13
|
The other day our code signing certificate expired. Having purchased a new certificate we now want to update our users to the latest version of our software that includes the new certificate. Now here's the problem, our users cannot install the new version. The update process uses AddinModule.CurrentInstance.CheckForUpdates(); and manages to go away and fetch the new application manifest but when it runs users are confronted with an error, the error summary shows us this error "The deployment identity does not match the subscription." Having compared the two .application files (before and after the new certificate) the only difference is in digest values, public key tokens, and version number.
How can we get our ClickOnce deployment to work correctly with the new certificate if the users with add-ins using the old certificate cannot upgrade? |
|
Inspirometer Developer
Posts: 34
Joined: 2017-10-13
|
We've managed to find the problem! There was another change that happened on our server - we enabled an HTTP to HTTPS rewrite rule. This meant that when the add-in tried updating the URL was redirected to HTTPS making the provider URL and update URL different, therefore failing the requirements for updating with different certificates. |
|
Andrei Smolin
Add-in Express team
Posts: 18791
Joined: 2006-05-11
|
Many thanks for sharing your finding with forum readers!
Andrei Smolin
Add-in Express Team Leader |
|