From 47ecd950b8f11d44e6581a1b9de30a54b140620e Mon Sep 17 00:00:00 2001 From: Kyle Brennan Date: Fri, 15 May 2020 16:54:19 -0700 Subject: [PATCH] Enhance details about user application keys. Fix #2672 --- doc/030_preparing_a_new_repo.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index 937ac1f51..15a0fa31c 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -442,6 +442,14 @@ dashboard on the "Buckets" page when signed into your B2 account: $ export B2_ACCOUNT_ID= $ export B2_ACCOUNT_KEY= +To get application keys, a user can go to the App Keys section of the Backblaze +account portal. You must create a master application key first. From there, you +can generate a standard Application Key. Please note that the Application Key +should be treated like a password and will only appear once. If an Application +Key is forgotten, you must generate a new one. + +For more information on application keys, refer to the Backblaze `documentation `__. + .. note:: As of version 0.9.2, restic supports both master and non-master `application keys `__. If using a non-master application key, ensure that it is created with at least **read and write** access to the B2 bucket. On earlier versions of restic, a master application key is required. You can then initialize a repository stored at Backblaze B2. If the