用于远程调用Mysql

Add remote user to Mysql from for exemple IP=remoteIP : mysql -u xxxx -p //local coonection to mysql mysql> GRANT ALL PRIVILEGES ON *.* TO 'theNewUser'@'remoteIP' IDENTIFIED BY 'passWord'; //Query OK, 0 rows affected (xx sec) mysql> FLUSH PRIVILEGES; //Query OK, 0 rows affected Allow remote access to Mysql (by default all externall call is not allowed): Edit /etc/mysql/mysql.conf.d/mysqld.cnf or /etc/mysql/my.cnf Change line: bind-address = 127.0.0.1 to bind-address = 0.0.0.0 Restart Mysql: /etc/init.d/mysql restart For The latest version of JDBC Driver, the JDBC : jdbc.url='jdbc:mysql://remoteIP:3306/yourDbInstance?autoReconnect=true&useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC' jdbc.user='theNewUser'

在我的情况下，原来是mysql-connector-java的版本太旧了。

在我的演示中，我像这样使用mysql-connector-java:

<dependency>
    <groupId>mysql</groupId>
    <artifactId>mysql-connector-java</artifactId>
    <version>5.1.9</version>
</dependency>

但是在开发环境中，我使用这个:

<dependency>
    <groupId>mysql</groupId>
    <artifactId>mysql-connector-java</artifactId>
    <version>5.1.31</version>
</dependency>

我的MySQL版本是5.1.48(是的，它是旧的，只是为了模仿产品版本)。所以我遇到了同样的错误。

既然找到了原因，解决办法也就找到了。匹配版本!

我同样的问题是通过以下步骤解决的:

访问my.cnf vi /etc/mysql/my.cnf 修改其bind-address "bind-address = 0.0.0.0" 重新启动MySQL sudo /etc/init.d / mysql重启

打开文件/etc/mysql/my.cnf: 更改以下参数为

' bind-address = 127.0.0.1

to

Bind-address = 0.0.0.0 #允许所有系统连接

在mysql中针对特定的IP地址执行以下命令->

grant all privileges on dbname.* to dbusername@'192.168.0.3' IDENTIFIED BY 'dbpassword';                      

如果你想访问所有的IP地址，运行下面的命令:

grant all privileges on dbname.* to dbusername@'%' IDENTIFIED BY 'dbpassword'; 

这也是MySQL正在消亡的原因。在我的例子中，我有一个查询触发了MySQL中的一个错误，所以每当执行查询时，服务器就会死机并重新启动。查看MySQL错误日志，看看是否发生了这种情况。 在我的例子中(MacOS上的Homebrew)，它位于/usr/local/var/mysql/<machinename>.err

因为我是在一个测试系统上看到的，所以我最终放弃并重新创建了我的数据库，这解决了问题，但我不敢想象如果它是在生产系统上，我会做什么。

如果Java试图通过SSL连接MySQL，但出现了错误，也可能发生此错误。(在我的例子中，我将Payara Server 5.193.1连接池配置为MySQL。)

有人建议设置useSSL=false。但是，由于Connector/J版本8.0.13，该设置已弃用。下面是MySQL连接器/J 8.0配置属性的摘录:

sslMode By default, network connections are SSL encrypted; this property permits secure connections to be turned off, or a different levels of security to be chosen. The following values are allowed: DISABLED - Establish unencrypted connections; PREFERRED - (default) Establish encrypted connections if the server enabled them, otherwise fall back to unencrypted connections; REQUIRED - Establish secure connections if the server enabled them, fail otherwise; VERIFY_CA - Like REQUIRED but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates; VERIFY_IDENTITY - Like VERIFY_CA, but additionally verify that the server certificate matches the host to which the connection is attempted. This property replaced the deprecated legacy properties useSSL, requireSSL, and verifyServerCertificate, which are still accepted but translated into a value for sslMode if sslMode is not explicitly set: useSSL=false is translated to sslMode=DISABLED; {"useSSL=true", "requireSSL=false", "verifyServerCertificate=false"} is translated to sslMode=PREFERRED; {"useSSL=true", "requireSSL=true", "verifyServerCertificate=false"} is translated to sslMode=REQUIRED; {"useSSL=true" AND "verifyServerCertificate=true"} is translated to sslMode=VERIFY_CA. There is no equivalent legacy settings for sslMode=VERIFY_IDENTITY. Note that, for ALL server versions, the default setting of sslMode is PREFERRED, and it is equivalent to the legacy settings of useSSL=true, requireSSL=false, and verifyServerCertificate=false, which are different from their default settings for Connector/J 8.0.12 and earlier in some situations. Applications that continue to use the legacy properties and rely on their old default settings should be reviewed. The legacy properties are ignored if sslMode is set explicitly. If none of sslMode or useSSL is set explicitly, the default setting of sslMode=PREFERRED applies. Default: PREFERRED Since version: 8.0.13

因此，在我的例子中，设置sslMode=DISABLED就是解决这个问题所需要的全部内容。 这是在一台测试机器上。但是对于生产环境，安全解决方案应该正确配置Java客户机和MySQL服务器以使用SSL。

注意，通过禁用SSL，您可能还必须设置allowPublicKeyRetrieval=true。(同样，从安全角度来看，这不是一个明智的决定)。进一步的信息提供在MySQL ConnectionString选项:

AllowPublicKeyRetrieval If the user account uses sha256_password authentication, the password must be protected during transmission; TLS is the preferred mechanism for this, but if it is not available then RSA public key encryption will be used. To specify the server’s RSA public key, use the ServerRSAPublicKeyFile connection string setting, or set AllowPublicKeyRetrieval=True to allow the client to automatically request the public key from the server. Note that AllowPublicKeyRetrieval=True could allow a malicious proxy to perform a MITM attack to get the plaintext password, so it is False by default and must be explicitly enabled.