Open jnweiger opened 4 months ago
Hmm if OAuth is enabled you should not get to that screen. You only get to that screen with basic auth disabled if the system is misconfigured.
24-06-26 17:15:13:621 [ info sync.networkjob.determineauthtype2 ]: Auth type for QUrl("https://ocXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.owncloud.works/remote.php/webdav/") is OCC::DetermineAuthTypeJob::AuthType::Basic
Correct. oauth is disabled.
So you are talking about a 100% theoretical and unsupported scenario?
Same when user gets disabled via e.g. occ user:disable bob
basic auth is unsupported? I still do most QA with basic auth.... :scream:
Why would you get invalid credentials reported if the server and your credentials are correctly setup?
That is the question, that I want to address with this ticket. In my understanding, the correct error message should be: "Client password authentication is disabled."
For extra confusion, the server UI and docs mix up: app token, token, auth token, app password, app passcode. It is all the same.
The client seems to display the error message it directly got from the server. Moving this ticket to core.
what should happen is documented here: https://doc.owncloud.com/server/next/admin_manual/configuration/server/config_sample_php_parameters.html#enforce-token-only-authentication-for-apps-and-clients-connecting-to-owncloud
Error messages are no nice - agreed. Changing them would be effort which we are not capable to invest at the moment.
Voting for won't fix
Seen with core 10.14.0 and destop client 5.3.1
Pre-submission Checks
Describe the QA issue
Basic auth can be prevented by
occ config:system:set token_auth_enforced --type boolean --value true
Client log says
Expected behaviour:
Steps to reproduce the issue
.
Screenshots
.
Expected behavior
No response
Actual behavior
No response