albertony 72227a0151 jottacloud: do not store username in config when using standard auth ... Previously, with standard auth, the username would be stored in config - but only after entering the non-standard device/mountpoint sequence during config (a feature introduced with #5926). Regardless of that, rclone always requests the username from the api at startup (NewFS). In #6270 (commit 9dbed02329) this was changed to always store username in config (consistency), and then also use it to avoid the repeated customer info request in NewFs (performance). But, as reported in #6309, it did not work with legacy auth, where user enters username manually, if user entered an email address instead of the internal username required for api requests. This change was therefore recently reverted. The current commit takes another step back to not store the username in config during the non-standard device/mountpoint config sequence (consistentcy). The username will now only be stored in config when using legacy auth, where it is an input parameter.		2022-07-25 18:23:09 +01:00
..
api	jottacloud: refactor timestamp handling	2022-04-27 13:41:39 +02:00
jottacloud_internal_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
jottacloud_test.go	build: fix up package paths after repo move	2019-07-28 18:47:38 +01:00
jottacloud.go	jottacloud: do not store username in config when using standard auth	2022-07-25 18:23:09 +01:00