Comments on: Input not an X.509 certificate

By: Mick T.

Mick T. — Mon, 05 Apr 2010 15:46:37 +0000

Thanks! You helped me figure out why I couldn’t import an updated certificate.

By: mBread

mBread — Thu, 25 Mar 2010 08:44:39 +0000

So, what the error is saying (or meaning to say) is “there is no certificate in the keystore with the alias you specified (or didn’t)”?

By: Andy

Andy — Tue, 23 Mar 2010 13:15:22 +0000

Maybe I’m blind, but what is the difference between the two lines???

By: Malcolm

Malcolm — Fri, 19 Mar 2010 10:10:48 +0000

Yep had the same problem. Thanks for wasting those 20 minutes, saved me alot more than that.

By: Joey

Joey — Tue, 12 Jan 2010 18:59:12 +0000

Thanks a lot! Going from Thawte’s documentation I thought I was supposed to import the certificate as a NEW alias, this article helped me figure out my mistake.

By: Giona

Giona — Wed, 18 Nov 2009 13:29:22 +0000

Thank you a lot Danie.

Why is everything having to do with Java always such a goddamn mess?

By: DallasRat

DallasRat — Fri, 11 Sep 2009 16:04:42 +0000

My p7b file contained the Signing cert and an Intermediate cert. Both had to be exported. see VeriSign Code Singing Support Article so11251. The p7b file had to be opened and each certificate exported to Base64. then the keytool took them (both Base64) without issue. Hope this helps someone.

By: danieroux

danieroux — Thu, 22 Jan 2009 20:05:00 +0000

Morten,

Thank you for your input!

By: W H

W H — Thu, 22 Jan 2009 16:17:25 +0000

Thanks! This was exactly my issue. You just made my day!

By: Morten Simonsen

Morten Simonsen — Wed, 21 Jan 2009 09:02:02 +0000

Read a comment on Thawte on this issue, and it seems like keytool is very strict about format. If you have anything in your certificate before —–BEGIN CERTIFICATE—– or anyting after —–END CERTIFICATE—–, then it might very well be a problem. (Tested on JDK 1.5.0_17)