自己管理型シャーディングされたクラスターをキーファイル認証に更新（ダウンタイムなし）

Create the adminstrator user.

Use the db.createUser() method to create an administrator user and assign it the following roles:

• clusterAdmin on the admin database

• userAdmin roles on the admin database

Clients performing maintenance operations or user administrative operations on the sharded cluster must authenticate as this user at the completion of this tutorial. Create this user now to ensure that you have access to the cluster after enforcing authentication.

admin = db.getSiblingDB("admin");
admin.createUser(
  {
    user: "admin",
    pwd: "<password>",
    roles: [
      { role: "clusterAdmin", db: "admin" },
      { role: "userAdmin", db: "admin" }
    ]
  }
);

Optional: Create additional users for client applications.

In addition to the administrator user, you can create additional users before enforcing authentication.. This ensures access to the sharded cluster once you fully enforce authentication.

db.getSiblingDB("marketing").createUser(
  {
    "user": "joe",
    "pwd": "<password>",
    "roles": [ { "role" : "readWrite", "db" : "marketing" } ]
  }
)

See データベースユーザー ロール for roles provided by MongoDB.

ユーザーを追加する方法の詳細については、「ユーザーを追加する 」チュートリアルを参照してください。 新しいユーザーを追加するときは、セキュリティに関するベストプラクティスを考慮してください。

Optional: Update client applications to specify authentication credentials.

While the sharded cluster does not currently enforce authentication, you can still update client applications to specify authentication credentials when connecting to the sharded cluster. This may prevent loss of connectivity at the completion of this tutorial.

mongosh  --username "joe" --password "<password>" \
  --authenticationDatabase "marketing" --host mongos1.example.net:27017

Create a new mongos configuration file.

For each mongos:

1. Copy the existing mongos configuration file, giving it a distinct name such as <filename>-secure.conf (or .cfg if using Windows). You will use this new configuration file to transition the mongos to enforce authentication in the sharded cluster. Retain the original configuration file for backup purposes.

2. To the new configuration file, add the following settings:

   • security.transitionToAuth set to true

   • security.keyFile set to the keyfile path.

     If using a different internal authentication mechanism, specify settings appropriate for the mechanism.

   security:
      transitionToAuth: true
      keyFile: <path-to-keyfile>

   The new configuration file should contain all of the configuration settings previously used by the mongos as well as the new security settings.

One at a time, restart the mongos with the new configuration file.

Follow the procedure to restart the mongos instance, one mongos at a time:

1. Connect to the mongos to shutdown.

2. Use the db.shutdownServer() method against the admin database to safely shut down the mongos.

   db.getSiblingDB("admin").shutdownServer()

3. 再起動 mongos with the new configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongos-secure.conf:

   mongos --config <path>/mongos-secure.conf

   where <path> represents the system path to the folder containing the new configuration file.

Repeat the restart process for the next mongos instance until all mongos instances in the sharded cluster have been restarted.

Create a new mongod configuration file.

For each mongod in the config server replica set,

1. Copy the existing mongod configuration file, giving it a distinct name such as <filename>-secure.conf (or .cfg if using Windows). You will use this new configuration file to transition the mongod to enforce authentication in the sharded cluster. Retain the original configuration file for backup purposes.

2. To the new configuration file, add the following settings:

   • security.transitionToAuth set to true

   • security.keyFile set to the keyfile path.

     If using a different internal authentication mechanism, specify settings appropriate for the mechanism.

   security:
      transitionToAuth: true
      keyFile: <path-to-keyfile>

One at a time, restart the mongod with the new configuration file.

Restart the replica set, one member at a time, starting with the セカンダリ members.

1. To restart the セカンダリ members one at a time,

   1. Connect to the mongod and use the db.shutdownServer() method against the admin database to safely shut down the mongod.

      db.getSiblingDB("admin").shutdownServer()

   2. Restart the mongod with the new configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the new configuration file.

   Once this member is up, repeat for the next セカンダリ member.

2. Once all the secondary members have restarted and are up, restart the primary:

   1. Connect to the mongod.

   2. Use the rs.stepDown() method to step down the primary and trigger an election.

      rs.stepDown()

      You can use the rs.status() method to ensure the replica set has elected a new primary.

   3. Once you step down the primary and a new primary has been elected, shut down the old primary using the db.shutdownServer() method against the admin database.

      db.getSiblingDB("admin").shutdownServer()

   4. Restart the mongod with the new configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the new configuration file.

削除 transitionToAuth from the mongos configuration files.

Remove the security.transitionToAuth key and its value from the mongos configuration files created during this tutorial. Leave the security.keyFile setting added in the tutorial.

security:
   keyFile: <path-to-keyfile>

Restart the mongos with the updated configuration file.

Follow the procedure to restart mongos instance, one mongos at a time:

1. Connect to the mongos to shutdown.

2. Use the db.shutdownServer() method against the admin database to safely shut down the mongos.

   db.getSiblingDB("admin").shutdownServer()

3. 再起動 mongos with the updated configuration file, specifying the path to the config file using --config. For example, if the updated configuration file were named mongos-secure.conf:

   mongos --config <path>/mongos-secure.conf

削除 transitionToAuth from the mongod configuration files.

Remove the security.transitionToAuth key and its value from the config server configuration files created during this tutorial. Leave the security.keyFile setting added in the tutorial.

security:
   keyFile: <path-to-keyfile>

One at a time, restart the mongod with the updated configuration file.

Restart the replica set, one member at a time, starting with the セカンダリ members.

1. To restart the セカンダリ members one at a time,

   1. Connect to the mongod and use the db.shutdownServer() method against the admin database to safely shut down the mongod.

      db.getSiblingDB("admin").shutdownServer()

   2. Restart the mongod with the updated configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the updated configuration file.

   Once this member is up, repeat for the next セカンダリ member.

2. Once all the secondary members have restarted and are up, restart the primary:

   1. Connect to the mongod.

   2. Use the rs.stepDown() method to step down the primary and trigger an election.

      rs.stepDown()

      You can use the rs.status() method to ensure the replica set has elected a new primary.

   3. Once you step down the primary and a new primary has been elected, shut down the old primary using the db.shutdownServer() method against the admin database.

      db.getSiblingDB("admin").shutdownServer()

   4. Restart the mongod with the updated configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the updated configuration file.

削除 transitionToAuth from the mongod configuration files.

Remove the security.transitionToAuth key and its value from the config server configuration files created during this tutorial. Leave the security.keyFile setting added in the tutorial.

security:
   keyFile: <path-to-keyfile>

One at a time, restart the mongod with the updated configuration file.

Restart the replica set, one member at a time, starting with the セカンダリ members.

1. To restart the セカンダリ members one at a time,

   1. Connect to the mongod and use the db.shutdownServer() method against the admin database to safely shut down the mongod.

      db.getSiblingDB("admin").shutdownServer()

   2. Restart the mongod with the updated configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the updated configuration file.

   Once this member is up, repeat for the next セカンダリ member.

2. Once all the secondary members have restarted and are up, restart the primary:

   1. Connect to the mongod.

   2. Use the rs.stepDown() method to step down the primary and trigger an election.

      rs.stepDown()

      You can use the rs.status() method to ensure the replica set has elected a new primary.

   3. Once you step down the primary and a new primary has been elected, shut down the old primary using the db.shutdownServer() method against the admin database.

      db.getSiblingDB("admin").shutdownServer()

   4. Restart the mongod with the updated configuration file, specifying the path to the config file using --config. For example, if the new configuration file were named mongod-secure.conf:

      mongod --config <path>/mongod-secure.conf

      where <path> represents the system path to the folder containing the updated configuration file.