Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Adding VCH to VIC appliance fails with error PEMKeyPair (56950)

Last Updated: 10/27/2020Categories: TroubleshootingTotal Views: 3083Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You see  messages similar to the following while adding VCH to VIC Administration portal using a custom CA certificate:

While adding VCH to the VIC  portal  using the custom CA certificate and encrypted private key .

" Error connecting to https://VCH00-00.abc.org: Unexpected error:org.abc.PKCS8EncryptedPrivateKeyInfo cannot be cast to org.abc.openssl.PEMKeyPair"

While adding VCH to the VIC  portal  using the custom CA certificate and decrypted private key :

"Error connecting to https://VCH00-00.abc.org: Unexpected error:org.abc.pkcs.PrivateKeyInfo cannot be cast to org.abc.openssl.PEMKeyPair"

Resolution

This issue occurs when the private key is in PKCS8 format.

Once you have the certificate generated. The certificate is in PKCS12 format and will have to be converted to pem format.

Execute a command similar to the following to convert the format of the certificate from pkcs12 to pem.

openssl pkcs12 -in TestCert.pfx -out TestCert_output.pem       (where TestCert.pfx is the name of the certificate that was generated and TestCert_output.pem is the name of the cert once it is converted to pem format)

A command similar to the following can be run to change the private key from PkCS8 to  RSA format.

openssl rsa -in pkcs8.pem -out rsakey.pem

Create the certificate credentials in the VIC portal:

In the browser open the VIC appliance portal : https://<vicapplianceFQDN>:8282/

Click on Administration > Identity Management

On the Credentials tab click on +credential and give a new name to the credentials. Beneath the name of new credential click on the certificate option.

In the Public certificate box, paste in the public certificate (Step1) and beneath that in the Private key box paste in the RSA private key (Step 2) and click on save.

Click on Home > Infrastructure > container host

Click on the +Container Hosts and in the Name section add the Name of the VCH to be added.

In the credentials dropdown, select the name of the credential created in Step 3 and click on save.

Note: If the error indicates that the private key is encrypted, you will need to decrypt the private key via a command similar to the following:

openssl pkey -in pkcs8.pem -out decrypted_key.pem

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Integrated Containers

VMware vSphere

Related Versions:

Take Our Survey

Support Assistant