If you want to install a medini extension, which does download additional packages from the internet (e.g. the scripted installer), this may fail with a message similar to this one: Provisioning exception org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
https://....../content.xml. This indicates that medini failed to download the external package, looked for alternative forms of such a package and finally ended up failing in downloading the last option content.xml - a file which actually does not exist on the server. Reason for this is likely an erroneous SSL certificate, as it was tweaked by your company's fire wall, especially if the following is in the error log: !MESSAGE Connection to ... failed on PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. Retry attempt 0 started Note: Background is that your company's fire wall wants to read the contents, but needs deep packet inspection for this, which means breaking the SSL connection and afterwards putting the contents into another SSL connection towards your computer. Browsers can detect this issue, but as the certificate of your company's firewall was configured as "that's ok" in your browser, it all works fine. This configuration is in this case not done for your Java Runtime Engine (JRE), which is used by medini Solution: Anyone that gets this error when using a Java application as medini and a accessing a web site using https inside its company, he has to make sure that the root certificate chain is known in the JRE cacerts certificate store. In other words: companies tend to sign their server certificates (required for https) with their own company root CA for some reasons (its cheaper?). But that means that the root CA and any intermediate CA must be known to the JRE which isn't in medini's JRE. See the answer to this article on stackoverflow.com for example:
https://stackoverflow.com/questions/21076179/pkix-path-building-failed-and-unable-to-find-valid-certification-path-to-requ Alternatively, if your company has its own (pre-configured) variant of a JRE, then please use this with medini (replace it in the "Program/jre" subfolder of medini). We hope that helps you in your case! Regards, Nils
