Desktop: TFA & nextcloudcmd

[ptman]

Expected behaviour

nextcloudcmd should work with TFA

Actual behaviour

nextcloudcmd doesn't work with TFA

Steps to reproduce

1. Enable TFA
2. run nextcloudcmd
3. get error

Client configuration

Client version: Nextcloud version 2.6.2-1

Operating system: Debian bullseye

OS language: English

Qt version used by client package (Linux only, see also Settings dialog): 5.12.5

Client package (From Nextcloud or distro) (Linux only): nextcloud-desktop-cmd/testing,now 2.6.2-1

Installation path of client: /usr/bin/nextcloudcmd

Server configuration

Nextcloud version: 17.0.1

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

02-12 16:45:08:356 [ warning nextcloud.sync.networkjob ]:   QNetworkReply::AuthenticationRequiredError "Error transferring https://.../remote.php/webdav/ - server replied: " QVariant(int, 401)
02-12 16:45:08:356 [ info nextcloud.sync.networkjob.lscol ]:    LSCOL of QUrl("https://.../remote.php/webdav/") FINISHED WITH STATUS "AuthenticationRequiredError Error transferring https://.../remote.php/webdav/ - server replied: "
02-12 16:45:08:356 [ warning nextcloud.sync.discovery ]:    LSCOL job error "Error transferring https://.../remote.php/webdav/ - server replied: " 401 QNetworkReply::AuthenticationRequiredError

[rullzer]

What is TFA?

[rullzer]

Ah two factor authentication.
Well be sure to use an apptoken then. Because your native password will indeed not work.

[ptman]

Excellent. How does one use an apptoken with nextcloudcmd?

[ptman]

Is nextcloudcmd supposed to be usable with apptokens?

[edent]

@ptman I use an app token with nextcloudcmd.

For example

nextcloudcmd -u "admin" -p "ABCD-1234-5678-EFGH" ~/nextcloud/ https://example.com/nextcloud