KB-1740 MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Parmida Borhani — Fri, 05 Oct 2018 03:52:26 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/5/2018 3:52:26 AM

Symptoms

On JBoss or Tomcat startup the following warning appears in the <JBOSS_HOME>/standalone/log/server.log or <APPIAN_HOME>/log/tomcat-stdOut.log:

"WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Last Reviewed: October 2018

Tags: database, mysql, infrastructure

KB-1740 MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Parmida Borhani — Thu, 04 Oct 2018 23:51:52 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 10/4/2018 11:51:52 PM

Symptoms

On JBoss or Tomcat startup the following warning appears in the <JBOSS_HOME>/standalone/log/server.log or <APPIAN_HOME>/log/tomcat-stdOut.log:

"WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Last Reviewed: October 2018

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Thu, 04 Oct 2018 09:22:28 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 10/4/2018 9:22:28 AM

Symptoms

On JBoss or Tomcat startup the following warning appears in the <JBOSS_HOME>/standalone/log/server.log or <APPIAN_HOME>/log/tomcat-stdOut.log:

"WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Last Reviewed: October 2018

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 14:45:21 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 2:45:21 PM

Symptoms

Cause

Action

Affected Versions

This article applies to Appian 17.1 and later

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 11:20:08 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 11:20:08 AM

Symptoms

On JBoss or Tomcat startup the following warning appears in the <APPIAN_HOME>/log/tomcat-stdOut.log or <JBOSS_HOME>/standalone/log/server.log:

"Tue Jul 31 05:28:21 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Last Reviewed: October 2018

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 11:18:42 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 11:18:42 AM

Symptoms

On JBoss or Tomcat startup the following warning appears in the <APPIAN_HOME>/log/tomcat-stdOut.log or <JBOSS_HOME>/standalone/log/server.log:

"Tue Jul 31 05:28:21 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 11:01:45 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 11:01:45 AM

Symptoms

On JBoss or Tomcat startup, and while they are running, the following warning appears in the <APPIAN_HOME>/log/tomcat-stdOut.log or <JBOSS_HOME>/standalone/log/server.log:

"Tue Jul 31 05:28:21 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string used by the application server.

Action

This warning is safe to ignore and doesn't impact the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 11:01:03 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 11:01:03 AM

Symptoms

On JBoss or Tomcat startup, and while they are running, the following warning appears in the <APPIAN_HOME>/log/tomcat-stdOut.log or <JBOSS_HOME>/standalone/log/server.log:

"Tue Jul 31 05:28:21 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string.

Action

This warning is safe to ignore and doesn't affect the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later

Tags: known issues, database, infrastructure

DRAFT KB-XXXX MySQL SSL warning "Establishing SSL connection without server's identity verification is not recommended"

Zach Puderbach — Tue, 02 Oct 2018 10:57:04 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:57:04 AM

Symptoms

On JBoss or Tomcat startup, and while they are running, the following warning appears in the <APPIAN_HOME>/log/tomcat-stdOut.log or <JBOSS_HOME>/standalone/log/server.log:

"Tue Jul 31 05:28:21 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

Cause

SSL is not used or explicitly disabled in the datasource url connection string.

Action

This warning is safe to ignore and doesn't affect the functionality of Appian.

Affected Versions

This article applies to Appian 17.1 and later