Setting Multicloud Object Gateway account credentials using CLI command

Use this procedure to set the Multicloud Object Gateway (MCG) account credentials using the command-line interface (CLI) command. You can update and verify the MCG account credentials manually by using the MCG CLI command.

Before you begin

Make sure that the following prerequisites are met:
  • A running Fusion Data Foundation cluster.
  • Download the MCG CLI binary from the customer portal and make it executable.
Note:
  • Choose the correct product variant according to your architecture.
  • Available platforms are Linux (x86_64), Windows, and Mac OS.

Procedure

  1. Run the following command to update the MCG account credentials: 
     noobaa account credentials <noobaa-account-name> [options]

    Example:

     noobaa account credentials admin@noobaa.io

    Example output:

     noobaa account credentials admin@noobaa.io
Enter access-key: [got 20 characters]
Enter secret-key: [got 40 characters]
INFO[0026] ❌ Not Found: NooBaaAccount "admin@noobaa.io"
INFO[0026] ✅ Exists: NooBaa "noobaa"
INFO[0026] ✅ Exists: Service "noobaa-mgmt"
INFO[0026] ✅ Exists: Secret "noobaa-operator"
INFO[0026] ✅ Exists: Secret "noobaa-admin"
INFO[0026] ✈️  RPC: account.update_account_keys() Request: {Email:admin@noobaa.io AccessKeys:{AccessKey:* SecretKey:}} WARN[0026] RPC: GetConnection creating connection to wss://localhost:33495/rpc/ 0xc000cd9980 INFO[0026] RPC: Connecting websocket (0xc000cd9980) &{RPC:0xc0001655e0 Address:wss://localhost:33495/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} INFO[0026] RPC: Connected websocket (0xc000cd9980) &{RPC:0xc0001655e0 Address:wss://localhost:33495/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} INFO[0026] ✅ RPC: account.update_account_keys() Response OK: took 42.7ms INFO[0026] ✈️ RPC: account.read_account() Request: {Email:admin@noobaa.io} INFO[0026] ✅ RPC: account.read_account() Response OK: took 2.0ms INFO[0026] ✅ Updated: "noobaa-admin" INFO[0026] ✅ Successfully updated s3 credentials for the account "admin@noobaa.io" INFO[0026] ✅ Exists: Secret "noobaa-admin" Connection info: AWS_ACCESS_KEY_ID :  AWS_SECRET_ACCESS_KEY : *

    Credential complexity requirements:

    Access key

    The account access key must be 20 characters in length, and it must contain only alphanumeric characters.

    Secret key

    The secret key must be 40 characters in length, and it must contain alphanumeric characters and "+" and "/".

    Example:

     noobaa account credentials my-account --access-key=ABCDEF1234567890ABCD --secret-key=ABCDE12345+FGHIJ67890/KLMNOPQRSTUV123456
  2. Run the following command to verify the credentials: 
     noobaa account status <noobaa-account-name> --show-secrets
    Remember: Each user must have a unique access key and secret key.