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

How to adjust the validity period on certificates generated by vCloud Availability 3.x appliances (79196)

Last Updated: 6/18/2020Categories: How toTotal Views: 2358Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

Certificates generated by vCloud Availability 3.x appliances expire after one year, by default, and can be easily regenerated as needed. However, there are some situations where the expiration needs to be extended or reduced to accommodate specific business requirements.

Resolution

Please note that making changes directly to the files referenced below introduces risks to the functionality of your implementation if there are any mistakes or misconfigurations. Moreover, there is no guarantee that these changes will be preserved upon the next system update and may need to be re-introduced at a future time.

In order to adjust the default certificate expiration, perform the following steps on each appliance that requires the change:

Log in as root via SSH or the console.

Navigate to the following location: /opt/vmware/h4/bin/

Take a backup of the sysboot.py file and note the file permissions.

Using the text editor of your choice, open the file and look for a section similar to the following:

...
def create_new_keystore():
'''
Creates a new public/private keypair, stored in a PKCS#12 container.
'''
log('Generating keystore %s' % keystore)

cmd = [
'/opt/jre/bin/keytool', '-genkey',
'-keysize', '2048',
'-keyalg', 'RSA',
'-sigalg', 'SHA256withRSA',
'-alias', alias,
'-storetype', 'PKCS12',
'-keystore', keystore,
'-storepass', kspass,
'-keypass', keypass,
'-validity', '365',
'-dname', 'CN=%s.vm, OU=Unknown, O=Unknown' % alias,
]
...

Adjust the validity parameter to accommodate your business requirements.

Once these changes have been completed, they will take effect the next time the certificate is regenerated on the appliance.

Related Information

For more information on managing certificates in vCloud Availability 3.5, see the Certificates Management section of the vCloud Availability documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
VMware Advanced Remote Management 4.4/5.0 ジェネラル サポート終了のお知らせ (78738)

KB
•
すべてのプラットフォームの VMware Verify Chrome アプリと Chrome 拡張機能の提供終了を発表 (78699)

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 vCloud Availability

Related Versions:

VMware vCloud Availability 3.5.x

VMware vCloud Availability 3.0.x

Take Our Survey

Support Assistant