• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How to make my browser trust my server certificate?

 
Ranch Hand
Posts: 264
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I made my TOMCAT run on https using http://www.mkyong.com/tomcat/how-to-configure-tomcat-to-support-ssl-or-https/

When I open https://localhost:8443/, it gives me a red colored page warning me, that the server certificate is not trusted by google chrome (that was expected).

Now, I want to make my google chrome trust the server certificate. I generated mkyong.cer file using keytool -export command

and then I tried to import it in client's trust store as follows.

(clientTrustStore.key is the output file, and mkyong.cer is the input file.)

I took reference of http://db.apache.org/derby/docs/dev/adminguide/cadminsslkeys.html for import command.

C:\>keytool -import -alias mkyong -file mkyong.cer -keystore clientTrustStore.key
Enter keystore password:
Re-enter new password:
Owner: CN=yong mook kim, OU=CDG, O=NSEL, L=NOIDA, ST=UP, C=IN
Issuer: CN=yong mook kim, OU=CDG, O=NSEL, L=NOIDA, ST=UP, C=IN
Serial number: 4f89351e
Valid from: Sat Apr 14 13:58:14 IST 2012 until: Fri Jul 13 13:58:14 IST 2012
Certificate fingerprints:
MD5: 3C:5F:CC:34:2B:BE:F3:18:67:3A:64:5B:FE:28:A3:C4
SHA1: DB:B0:45:21:5C:2E:1A:50:1A:84:F1:EE:12:47:40:71:9F:3D:DF:6B
Signature algorithm name: SHA1withRSA
Version: 3
Trust this certificate? [no]: yes
Certificate was added to keystore




Even after this, I am still getting that warning when i open https://localhost:8443/

Can someone please explain this behavior, or if I am doing something wrong?
 
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here's the first link I got when I googled your question: http://groups.google.com/a/googleproductforums.com/forum/#!topic/chrome/1b7V3cs7BS4. It appears to me that the answer given there is "Use Internet Explorer to make it trusted and then Chrome will automatically trust it", but you can read the whole thread which does contain more information than just that.
 
Yogesh Gandhi
Ranch Hand
Posts: 264
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Paul for taking out some time and answering.

I have researched on net and studied something about this.

I have created one post from my understanding and observation.

Might help someone

Here you go :

http://javakafunda.blogspot.in/2012/04/how-to-make-my-browser-trust-my-server.html
 
reply
    Bookmark Topic Watch Topic
  • New Topic