General

Re: InfoPath Code Signing Certificate expired

Squez — Tue, 03 Feb 2015 16:02:09 GMT

Reviving an old question here because my cert just expired. Can you tell me how I can renew my self-signed cert? My knowledge of certs is somewhat limited, so any additional information you can provide would be very helpful. Thanks!

Re: InfoPath Code Signing Certificate expired

Aldo76 — Mon, 03 Jun 2013 15:39:19 GMT

Thank you for your response Patrick,

I couldn't wait for an answer here so I opted for a new certificate. Thus, each time I do a change to a template, I remove the expired certificate and I use the one I generated.

Thanks again!

Re: InfoPath Code Signing Certificate expired

Patrick Halstead — Sun, 02 Jun 2013 20:54:53 GMT

Hi Aldo,

Renewing the certificate with the same key should be sufficient. You should not have to republish the form templates. If you add a new certificate, you will have to add to each template and republish.

You may not need to have full trust forms. We only see a real need for full-trust forms in 1-2% of scenarios. We do see a lot of InfoPath solutions that are full trust when they don't need to be.

We do provide quick consulting help if you need it.

InfoPath Code Signing Certificate expired

Aldo76 — Tue, 28 May 2013 13:37:51 GMT

Hello! I recently took over a project consisting in maintaining InfoPath forms in a SharePoint 2007 environment. Forms open with client application, thus not browser-enabled. It turns out that most form templates are set on full-trust and the code signing certificate, issued by the company's CA, has expired. Thus, when I try to edit a form template from inside a SharePoint form library, I get a message from InfoPath Designer stating that the certificate has expired and that I need to remove it from the form template before proceeding to edit it. I have never been in this situation before so I want to know what the best practice is in this situation. Should I just renew the Certificate in the Certificates MMC? If yes, should it be renewed with the same key or a different key? Also, If I renew the Certificate, will existing form templates continue to function seamlessly or will they require that I re-publish them all again? (there are dozens of form libraries in the SharePoint farm). I thought that a new code signing certificate would be a better approach, as this will allow me to update the code and the form template's code signing certificate one at a time. Am I right here? What about the existing submitted forms by end-users. Today they are able to open them, even if the code signing certificate has expired. Does the change of code signing certificate affect end-users in any way? Sorry for the amount of questions. I haven't found any resource on the web that could help me in this particular problem.