get-the-client-integration-plug-in-running-in-vsphere-web-client-6-x


The headline of this blog post might sound simple, but it can be extremely annoying to get the Client Integration Plug-in running to import virtual appliances.

No matter if you use IE, Chrome or Firefox you can find yourself surrounded with error messages and information that your you Client plugin needs to be installed (despite the fact, that you just installed it some minutes ago and restarted your browser).

A very common message is also "The VMware Client Integration Plugin has updated its SSL certificate in Firefox. Please Restart Firefox." 

The reason is the required NPAPI support, that most browser don´t support anymore. It even gets worse, as latest browser versions don´t allow to re-enable the NPAPI support.

Most of the errors are fixed in vSphere 6.5 but still existing in all versions before.

As many people still run vSphere 6.0 I want to guide you through the Firefox installation, to make sure the Client Integration Plug-In is working.

Install Firefox

Unfortunately, It´s not possible anymore to enable NPAPI using a Firefox version older than 52. Therefore, we need to install Firefox 52 first and uninstall any newer Version. Please be aware that Firefox autoupdates by default, so more often than not, you need to uninstall first to install an older version.

FireFox uninstall

FireFox uninstallation.

Just to make sure, you´re going to use an outdated technology. But its the only way I found that always works.

You might want to consider the Firefox Extended Support Edition that is community driven and supports NPAPI 12 month longer. https://www.mozilla.org/en-US/firefox/organizations/

Download Firefox version 52 for your OS here: https://ftp.mozilla.org/pub/firefox/releases/52.0/ and install the software. Please make sure to disable the maintenance service in the installation wizard.

Install Firefox

Select Custom during the installation and disable the "Install Maintenance Service" Box.

Deactivate Maintenance Service

Change Update Settings

First thing to change after the first launch is the update setting.

Firefox change settings

Click the icon top right and select Options.

Disable update Firefox

Disable the automatic update.

Firefox setting to enable NPAPI

To change the NPAPI settings in Firefox and enable Flash, Silverlight plugins, just type about:config to open the advanced settings.

Firefox settings

Accept the risk and continue to the settings page. Then right click into the list and select New-Boolean

Change NPAPI settings in Firefox

Type in plugin.load_flash_only and select false.

Firefox setting plugin.load_flash_only

Change to false

Then restart Firefox.

Install Flash

Make sure to install Flash.

Install Adobe Flash

Install Client Integration Plugin

Visit your VMware vCenter Web Client and install the Client integration plugin (best is to start Firefox using an administrative account).

Download Client Integration Plugin

Install Client Integration Plugin

When everything has been installed successful, you can log into your VMware vSphere Web client and use Client Integration plugin functions like Deploy OVF.

Deploy OVF function within the vSphere Web Client

Just make sure to allow the Plugin to do its job, by clicking allow for the https protocol access.

allow client access

That’s it and you should have all up and running.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.