CA Certificate Issue
Hi All,
Issue: In user mode the application is thorwing a pop-up regarding "CA certificate". I tried importing the certificate using following cmds:
certmgr.exe -add -c "<cert-file>" -s -r localMachine root
Certmgr.exe -c YourCertificate -s TrustedPublishers -add
It is showing "success", but the pop-up is coming again in user mode, and prompting to import the certificate again.
Anyone has any idea how to resolve this?
Thanks,
DN
Issue: In user mode the application is thorwing a pop-up regarding "CA certificate". I tried importing the certificate using following cmds:
certmgr.exe -add -c "<cert-file>" -s -r localMachine root
Certmgr.exe -c YourCertificate -s TrustedPublishers -add
It is showing "success", but the pop-up is coming again in user mode, and prompting to import the certificate again.
Anyone has any idea how to resolve this?
Thanks,
DN
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Posted by:
dnmech
13 years ago
Posted by:
anonymous_9363
13 years ago
Posted by:
tron2ole
13 years ago
I am dealing with a simular issue where I have created my 2 certificates and need to add them as CAs into my MSI.
I had the certmgr.exe in the binary so my CA source linked to the certmgr in the bonary table and the Type is 3074.
Target was -add c:\temp\abc.cer -c -s -r LocalMachine TrustedPublisher
Works fine using the /qn switch "although" I see a couple of cmd windows popup and exit very quickly.
Therefore, via SCCM deployment testing....the package did not work....and I suspected it would not work too.
Testing via psexec -i -s cmd to execute cmd as system context.
I am trying another method....but I am suspicious.
Add the certmgr in the c:\windows dir.
The CA will use the SystemFolder in the Source - call cmd.exe /c c:\windows\certmgr.exe -add c:\temp\abc.cer -c -s -r LocalMachine TrustedPublisher
Type 3106
Am I going about it in the right way....not sure?
I had the certmgr.exe in the binary so my CA source linked to the certmgr in the bonary table and the Type is 3074.
Target was -add c:\temp\abc.cer -c -s -r LocalMachine TrustedPublisher
Works fine using the /qn switch "although" I see a couple of cmd windows popup and exit very quickly.
Therefore, via SCCM deployment testing....the package did not work....and I suspected it would not work too.
Testing via psexec -i -s cmd to execute cmd as system context.
I am trying another method....but I am suspicious.
Add the certmgr in the c:\windows dir.
The CA will use the SystemFolder in the Source - call cmd.exe /c c:\windows\certmgr.exe -add c:\temp\abc.cer -c -s -r LocalMachine TrustedPublisher
Type 3106
Am I going about it in the right way....not sure?
Posted by:
dannyarya
13 years ago
@ tron2ole - If you are doing installation of machine based Certificate then it'll work fine.
you can also use type : 1106 CA
For Example:
CustomAction Table-
PublicPrimaryCertificate | 1106 | certmgr.exe | -add -c "[INSTALLDIR]Verisign Class 1 Public Primary CA - G3.cer" -s -r LocalMachine ROOT
IndividualSubscriberCertificate | 1106 | certmgr.exe | -add -c "[INSTALLDIR]Verisign Class 1 Individual Subscriber CA - G3.cer" -s -r LocalMachine CA
you can also use type : 1106 CA
For Example:
CustomAction Table-
PublicPrimaryCertificate | 1106 | certmgr.exe | -add -c "[INSTALLDIR]Verisign Class 1 Public Primary CA - G3.cer" -s -r LocalMachine ROOT
IndividualSubscriberCertificate | 1106 | certmgr.exe | -add -c "[INSTALLDIR]Verisign Class 1 Individual Subscriber CA - G3.cer" -s -r LocalMachine CA
Posted by:
rich0864
13 years ago
Posted by:
tron2ole
13 years ago
[8|]
WOW - I thought that I would just add the two blob registry keys: HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\
So the MSI only contains those two reg keys....installs fine and tested in system context....
In SCCM....does not deploy the reg keys....weird.....
I am now added the keys in a script and added as a CA in the MSI to test....strange though....
Could be one to be thrown to the SCCM forum....
WOW - I thought that I would just add the two blob registry keys: HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\
So the MSI only contains those two reg keys....installs fine and tested in system context....
In SCCM....does not deploy the reg keys....weird.....
I am now added the keys in a script and added as a CA in the MSI to test....strange though....
Could be one to be thrown to the SCCM forum....
Comments:
-
Make sure the "WriteRegistryValues" (containing this BLOB) will be executed earlier in the "InstallExecuteSequence" table than the "MsiInstallDrivers" or CA where drivers are being installed. - mduiker 8 years ago
Posted by:
anonymous_9363
13 years ago
Posted by:
tron2ole
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.