|
Posted by Steven L Umbach on March 10, 2006, 9:02 pm
Please log in for more thread options Thanks for reporting back what worked and sorry to give you a link that was
a wrong turn! --- Steve
>I tried to post this yesterday, but it didn't come through. Apologies if
> this is a repeat.
>
> After much effort, and a little tinkering (full story on my blog at
> http://msmvps.com/alunj), I found that the answer is that you don't use a
> CTL, despite whatever Microsoft's documentation may say on the matter.
>
> The way to deploy a code signing certificate to the Trusted Publishers
> store
> is to create a Group Policy Object with Software Restriction Policies
> added.
> Add a Certificate Rule for each certificate that you're deploying, with
> the
> certificate set to the code-signing certificate, and the Security Level
> set
> to "Unrestricted".
>
> If you also need to deploy the root CA certificate, you can do that as
> specified in the Microsoft documentation as a Trusted Root.
>
> Alun.
> ~~~~
>
> "Alun Jones" wrote:
>
>> Okay, so I've signed the form template in InfoPath, and posted it to a
>> Sharepoint Forms Library.
>>
>> Now, my users are asked if they want to trust the certificate.
>>
>> Since this is in an enterprise, I'd really like it if they already
>> trusted
>> the certificate.
>>
>> Obviously, there's two certificates I have to deploy at my users'
>> systems -
>> one is the certificate with which I signed the template, and this must be
>> installed into "Trusted Publishers"; the other is the root CA
>> certificate,
>> which needs to be installed in "Trusted Root CAs".
>>
>> Is there documentation that lists how I can roll out these certificates
>> to
>> an enterprise - is this something a Group Policy Object can do?
>>
>> Up until now, I've been more on the developer side of certificates and
>> PKI,
>> so the administrative side is new to me.
|