Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Replacing the vRealize Automation default SSL certificate with Microsoft CA signed certificate fails due to errors in the v3 critical extensions section of the certificate (76089)

Last Updated: 1/30/2020Categories: TroubleshootingTotal Views: 11861Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

Errors similar to are seen:

Certificate with sha256 sum: SHA256_THUMBPRINT have errors in section 'v3_extensions'["Unable to parse certificate's ['v3_extensions']['critical'] section. ", "Unable to parse certificate's ['v3_extensions']['critical'] section. "]

Purpose

Replacing the default SSL certificate of vRealize Automation from vRealize Suite Lifecycle Manager fails with error related to "Unable to parse certificate's ['v3_extensions']['critical'] section."

Cause

Microsoft CA signing process introduces v3 extensions which are not understood by vRealize Automation and certificate verification process marks the certificate as invalid.

Resolution

This issue is resolved in vRealize Automation 8.0.1.

Workaround

To work around this issue, you can force install of the certificate with the following steps:

Verify that your certificate covers the following criteria:

Includes all of the appliances hostnames as subject alternative names (SANs)

Includes the load-balancer fully qualified domain name (FQDN) as a subject alternative name (SAN)

Doesn't include any wildcard (*) addresses

Compose a PEM file (Private Key and Entire Trust Chain) which should include the following in the same order:

The RSA encrypted private key

The Primary certificate in Base 64 format

All of the Intermediate certificates in Base 64 format

The Root CA certificate in Base 64 format

Example:
-----BEGIN RSA PRIVATE KEY-----
(Private Key)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(Primary SSL certificate)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Intermediate certificate)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Root CA certificate)
-----END CERTIFICATE-----

SSH to one of the appliances and run the following command:

# vracli certificate ingress --validate stdin --parse

Paste the entire PEM which we composed in step 2 and press CTRL+D.

This should result in the error below:

Certificate with sha256 sum: SHA256_THUMBPRINT have errors in section 'v3_extensions'["Unable to parse certificate's ['v3_extensions']['critical'] section. ", "Unable to parse certificate's ['v3_extensions']['critical'] section. "]

You can ignore errors related to v3_extensions - critical section, however if you receive different verification errors please do not proceed further and go back to step 1 and 2 to verify your PEM.

Run command the following command in order to force the certificate installation:

# vracli certificate ingress --set stdin --force

Paste the PEM, same as step 2, and press CTRL+D

Apply the PEM on all appliances by running the following command:

# /opt/scripts/deploy.sh

Wait until re-deployment is completed. Once ready you should see a message similar to the one below:

Prelude has been deployed successfully

Verify the certificate has been changed successfully by navigating to the vRealize Automation portal

You can proceed with replacing the VMware Identity Manager certificate from vRealize Suite Lifecycle Manager

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
使用 vRealize Automation REST API 在重新配置实施后操作期间配置磁盘 (76069)

KB
•
VMware vSAN 仮想環境での IBM Spectrum Protect (76071)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 8.x

Take Our Survey

Support Assistant