@@ -997,10 +997,6 @@ default.
997
997
write data as temporary files to disk. To review the MongoDB Atlas free
998
998
tier constraints, see the `MongoDB Atlas manual <https://docs.atlas.mongodb.com/create-new-cluster/#service-m0-free-tier-limitations>`_.
999
999
1000
- To connect the {+download-center-bi+}
1001
- to an Atlas cluster, you must provide :binary:`~bin.mongosqld` with a
1002
- ``.pem`` key file.
1003
-
1004
1000
:binary:`~bin.mongosqld` can use any valid TLS certificate issued by a
1005
1001
certificate authority, or a self-signed certificate. If you use a
1006
1002
self-signed certificate, although the communications channel will be
@@ -1013,38 +1009,39 @@ MySQL client to verify the server's identity.
1013
1009
For *testing* purposes, you can create a ``.pem`` key file named ``test.pem``
1014
1010
using the ``openssl`` tool:
1015
1011
1016
-
1017
1012
.. code-block:: sh
1018
1013
1019
1014
openssl req -nodes -newkey rsa:2048 -keyout test.key -out test.crt -x509 -days 365 -subj "/C=US/ST=test/L=test/O=test Security/OU=IT Department/CN=test.com"
1020
1015
cat test.crt test.key > test.pem
1021
1016
1022
- Start :binary:`~bin.mongosqld` with the :option:`--auth
1023
- <mongosqld --auth>` and :option:`--sslPEMKeyFile
1024
- <mongosqld --sslPEMKeyFile>` options.
1025
-
1026
- If you named your key file ``test.pem`` as in the previous example, you
1027
- can run the following, substituting your :ref:`schema file <drdl>` and
1028
- cluster URI:
1017
+ Start :binary:`~bin.mongosqld` with the following options:
1029
1018
1030
- .. note:: Do not specify a username and password in :option:`--mongo-uri`. The
1031
- connection string should only contain the list of servers.
1019
+ - :option:`--mongo-ssl <mongosqld --mongo-ssl>`
1020
+ - :option:`--auth <mongosqld --auth>`
1021
+ - :option:`--sslPEMKeyFile <mongosqld --sslPEMKeyFile>`
1022
+ - :option:`--mongo-uri <mongosqld --mongo-uri>`
1023
+ - :option:`--sslMode <mongosqld --sslMode>`
1024
+ - :option:`--mongo-username <mongosqld --mongo-username>`
1025
+ - :option:`--mongo-password <mongosqld --mongo-password>`
1032
1026
1027
+ If you named your key file ``test.pem`` as in the previous example, you
1028
+ can run the following, substituting your cluster URI and login
1029
+ credentials:
1033
1030
1034
1031
.. code-block:: sh
1035
1032
1036
1033
mongosqld --mongo-ssl \
1037
1034
--auth \
1038
1035
--sslPEMKeyFile test.pem \
1039
- --schema <schema.drdl> \
1040
1036
--mongo-uri <uri> \
1041
- --sslMode allowSSL
1037
+ --sslMode allowSSL \
1038
+ --mongo-username <username> \
1039
+ --mongo-password <password>
1042
1040
1043
1041
Pass your username, password, and authentication database to your SQL
1044
1042
client. For example, using ``mysql`` without verifying your :binary:`~bin.mongosqld`
1045
1043
server certificate:
1046
1044
1047
-
1048
1045
.. code-block:: sh
1049
1046
1050
1047
mysql --host <mongosqld-host> --port <mongosqld-port> -u <username>?source=admin -p --ssl-mode required --enable-cleartext-plugin
0 commit comments