thawte

I'm not the most advanced AWS user there is, and have come across a bit of a roadblock. I've got 2 Elastic Beanstalk Environments, each with a Load Balancer, 2 EC2 instances and they share a RDS instance. One environment is for Development and the other for Production. I have purchased a wildcard SSL certificate from Thawte, and would like to install it on both the Development and Production environments. I've gone through other threads about adding SSL certificates in AWS, but the admin interface has changed since they were written so I've been going round in circles trying to figure it out.

I'm trying to configure a Tomcat server with SSL. I've generated a keypair thus: $ keytool -genkeypair -alias tomcat -keyalg RSA -keystore keys Next I generate a certificate signing request: $ keytool -certreq -keyalg RSA -alias tomcat -keystore keys -file tomcat.csr Then I copy-paste the contents of tomcat.csr into a form on Thawte's website, asking for a trial SSL certificate. In return I get two certificates delimited with -----BEGIN ... -----END , that I save under tomcat.crt and thawte.crt . (Thawte calls the second certificate a 'Thawte Test CA Root' certificate). When I try to import

Trying to install thawte ssl onto Azure. Followed the steps as listed here and found that the certificate shows "The issuer of this certificate could not be found" I found this link that talks about the need for an intermediate certificate. How would this be applicable while deploying a web role onto Azure. Should the intermediate files be exported as pfx and uploaded to the certificate store. Do we need to specify this in the certificates section of the config file as well? Any suggestions would be greatly appreciated. EDIT Trying to export the intermediate pem file results in a .cer file. Is

I'm trying to sign an ActiveX control with a code signing certificate issued by Thawte. I was able to successfully sign the control using signtool.exe. When I look at the file properties, it says "The certificate in the signature cannot be verified." When I view the certificate it says "Windows does not have enough information to verify the certificate." On the certification path tab, it says "The issuer of this certificate cannot be found." In internet explorer, the certificate is recognized as signed but the user receives warnings that the publisher is not verified. I've tried creating a