Wednesday, April 9, 2014

Input not an X.509 certificate

Today I want to post a resolution for the certification import process of vCloud Director.

Most of the time it runs smoothly, you can follow KB1026309 and you will have no problems at all.

But sometimes you stumble with a weird issue that takes some time to figure out what went wrong.
I went into one of these situations past week. Then I was wondering why not share with you guys and maybe save some precious minutes of your time.

Let’s clarify a little bit the scenario.

I was implementing a vCloud solution on a client.
The client requested a wildcard certificate from it’s Certificate Authority company. He then sent me back the root, intermediate and wildcard certificates.

As I always do, I took the individual codes and saved them as .CER.
Copied them to the cell and started the import process.

No problem with ROOT and Intermediate certificates, but when I tried to import the wildcard certificate I got the error:
Keytool error: java.lang.Exception: Input not an X.509 certificate

After some troubleshoot I realize there was a space after each end of line on my file.

 After I deleted the space the import process was successfully.
I can only imagine there was something wrong with the format of the file when I saved it.

I hope you don’t cross this issue, but in case you do here’s how to fix it ; )

No comments:

Post a Comment

Who am I

My photo
I’m an IT specialist with over 15 years of experience, working from IT infrastructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Consulting Architect, helping customers to embrace the Cloud Era and make them successfully on their journey. Despite the fact I'm a VMware employee these postings reflect my own opinion and do not represents VMware's position, strategies or opinions. Reach me at @dumeirell

Most Viewed Posts

Blog Archive