Generalhttps://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)Digital Certificate Renewal Procedurehttps://www.infopathdev.com:443/forums/thread/5450.aspxThu, 16 Mar 2006 14:49:38 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:5450johngidd0https://www.infopathdev.com:443/forums/thread/5450.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=5450Given a situation where a deployed form is signed with a digital certificate which is also installed/deployed to the workstations where said form is invoked, is there a means to renew a certificate such that the deployed form will not require "update" to function with the new certificate. <br /><br />I am not responsible for registration of certificates at my current and do not claim to know much about the certificates in general. <br /><br />After a recent update to a certficate used to deploy the infopath forms at this location, I noticed that forms originally signed using the older certificate now required physical intervention to update the signed certificate through the infopath designer. <br /><br />If you renew a certificate with the original key(which I believe is an optional selection during renewal) should the forms signed with the old certificate not work with the new certificate when deployed to the workstations?<br /><br />Ignorant of the certificate registration process, I am just curious if anyone can confirm that its simply a "procedureal" issue with how the certificates are renewed, but the renewal should allow old signed infopath forms to continue functioning I would think. <br /><br />Provided that this seems reasonable and others can confirm that this is a certificate renewal issue, I will have those responsible for the certificates at this location review the process in greater detail. Just making sure I'm not sending them on a bogus task, but seems to me something was missed in the certificate renewal perhaps.<br /><br />