Smartdocs 2.1.0 plugin -Dmaven.wagon.http.ssl.insecure=true doesnt work

With the smartdocs 2.1.0 plugin even with this -Dmaven.wagon.http.ssl.insecure=true option set , this error occurs. This is not the case with the smartdoc 2.0.1 plugin.

Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty							

Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Any suggestions.

Thanks

Mehedi

0 2 541
2 REPLIES 2

@Mehedi Hashir

Have not used this, so not really sure. Did you include this dependency to your pom.xml ?

Are you trying to bypass / authenticate the Corporate proxy ?

Sri,

The option -Dmaven.wagon.http.ssl.insecure=true is inherited and available in any maven pom.

Here is what i have till now .

mvn install -Pdev -Dpropfile=$properties -Dapigee.smartdocs.config.options=update -Dmaven.wagon.http.ssl.insecure=true -Djavax.net.ssl.trustStore=/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security/cacerts -Djavax.net.ssl.trustStorePassword=changeit -Djavax.net.ssl.trustStoreType=jks -Djavax.net.debug=ssl:handshake:verbose:keymanager:trustmanager -Djava.security.debug=access:stack

WorkAround

Installed the truststore with ca certificates loaded, on some linux distros like alpine or chromeos , the certificate store is not installed by default.

Error only for com.apigee.smartdocs.config:apigee-smartdocs-maven-plugin:2.1.0:apidoc

[ERROR] Failed to execute goal com.apigee.smartdocs.config:apigee-smartdocs-maven-plugin:2.1.0:apidoc (smartdocs-deploy) on project DeveloperPortal: Execution smartdocs-deploy of goal com.apigee.smartdocs.config:apigee-smartdocs-maven-plugin:2.1.0:apidoc failed: Update failure: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Question is

Why the -Dmaven.wagon.http.ssl.insecure=true works with smartdocs plugin 2.0.1 but not smartdocs plugin 2.1.0 ?

For smartdocs-maven-plugin:2.1.0 is the option to use SSL being forced inspite of -Dmaven.wagon.http.ssl.insecure=true

Let me know if you'd like more detailed logs for each scenario.

Thanks

Mehedi