Tried just uploading the .CER generated by windows 2008 without running the certutil encode function or worrying about the .pem file extension and Wallah! It WORKS!! (thanks Paul for the hint)
On Apr 18, 6:22 pm, OffSiteCare <[email protected]> wrote: > At Paul's suggestion now the steps followed are: > 1. Double-clicked on certificate > 2. clicked the details tab > 3. clicked copy to file button > 4. click next at the certificate export wizard > 5. No, do not export the private key selected by default > 6. click next > 7. selected base-64 encoded X.509(.CER) > 8. click next > 9. gave it a file name: testgooglehealth.cer > 10. click next > 11. verified file name, Export keys no, include all certificates in > the certification path no, file format base-64 encoded X.509 > 12. click finish > 13. launch DOS window > 14. ran certutil -encode TestGoogleHealth.pfx TestGoogleHealth.pem > 15. uploaded file to Google Health manage domain, STILL GETTING > INVALID CERTIFICATE > > On Apr 18, 6:09 pm, "Paul (Google)" <[email protected]> wrote: > > > > > > > > > Welcome to the Health Developers' Forum! > > > From the process you described, it sounds like you might be trying to upload > > a PEM encoded PKCS#12 file, which would contain your private key and public > > key certificate. You can verify this by viewing the PEM file in a text > > editor. The Manage Domains tool only needs your public key certificate, so > > the file should NOT contain a "RSA PRIVATE KEY" section, only a > > "CERTIFICATE" section. > > > I hope this helps! > > > Paul (Google) -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
