Rickey Whitworth's Blog

We’ve been working on an Infopath form that needed to be signed. In the past, our
signed infopath forms were rolled out to IT Staff, and we had no problem clicking
on the Security Warning popup box that appears the first time (my apologies to Alun
Jones Security MVP for being lazy and taking this screenshot from his site. )

 

Since our new form was being rolled out to the company, we didn’t want to have this
window appear for everyone, (again, Alun gives a good explanation of why you wouldn’t
want to do this) so we were trying to find a way to get the certificate added to the
Trusted Publishers list on every computer. The article below explains the process,
and I am happy to say it worked great for us.

Excerpt:

I found myself tasked with publishing an Infopath Form on a Sharepoint site. Easy
enough, except that if you want the Form to do anything interesting, you have to give
it “Full Trust” (a phrase that should put shivers up the spine of anyone working in
security). To make sure that your users fully trust the Form, you have to sign it,
and you do that using a certificate whose purpose is to sign code (not document signing,
because the Form is really code, not a document).
Great – that’s easy.
Your company should have a root certificate authority for enterprise certificates,
and there should be an enterprise-wide certificate for code signing. They’re easy
to create.
The non-easy part comes next, as you realise what the user experience is going to
be.

Tales
from the Crypto : Why is PKI so hard?.

Random Posts