From 76532408ef0e3e0d089648140f068bab7be42a54 Mon Sep 17 00:00:00 2001 From: James Carpenter Date: Sat, 9 Feb 2019 09:00:05 +0000 Subject: [PATCH] b2: Application Key usage clarifications --- docs/content/b2.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/content/b2.md b/docs/content/b2.md index c2a3b9eaa..1652750b8 100644 --- a/docs/content/b2.md +++ b/docs/content/b2.md @@ -16,9 +16,11 @@ Here is an example of making a b2 configuration. First run rclone config -This will guide you through an interactive setup process. You will -need your account number (a short hex number) and key (a long hex -number) which you can get from the b2 control panel. +This will guide you through an interactive setup process. To authenticate +you will either need your Account ID (a short hex number) and Master +Application Key (a long hex number) OR an Application Key, which is the +recommended method. See below for further details on generating and using +an Application Key. ``` No remotes found - make a new one @@ -102,10 +104,10 @@ You can use these with rclone too; you will need to use rclone version 1.43 or later. Follow Backblaze's docs to create an Application Key with the required -permission and add the `Application Key ID` as the `account` and the +permission and add the `applicationKeyId` as the `account` and the `Application Key` itself as the `key`. -Note that you must put the Application Key ID as the `account` - you +Note that you must put the _applicationKeyId_ as the `account` – you can't use the master Account ID. If you try then B2 will return 401 errors.