Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-685

new useSSL parameter option only for remote hosts

Details

    Description

      I'm tring to setup failover configuration with multiple hosts. I would like connector to use unsecure connection to localhost and secure connection to other machines.

      Add new useSSL paramter option remote. This setting will use ssl for connections to remote host like 10.0.0.2 but will not use it for localhost and 127.0.0.1 etc.

      BTW useSSL=true and localSocket throws NullPointerException at AbstractConnectProtocol.java:709

      Attachments

        Activity

          diego dupin Diego Dupin added a comment -

          Joint to point: useSSL and localSocket NPE is solved by this commit

          diego dupin Diego Dupin added a comment - Joint to point: useSSL and localSocket NPE is solved by this commit
          diego dupin Diego Dupin added a comment -

          now, configuration permit setting sslMode per host.
          Example :
          "jdbc:mariadb:sequential://address=(localSocket=/socket),address=(host=10.0.0.1)(port=3306)(sslMode=verify-full)/DB"

          In the previous example, unix socket will be used, and host 10.0.0.1 with ssl if unix socket is not available.

          diego dupin Diego Dupin added a comment - now, configuration permit setting sslMode per host. Example : "jdbc:mariadb:sequential://address=(localSocket=/socket),address=(host=10.0.0.1)(port=3306)(sslMode=verify-full)/DB" In the previous example, unix socket will be used, and host 10.0.0.1 with ssl if unix socket is not available.

          People

            diego dupin Diego Dupin
            PavelCibulka Pavel Cibulka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.