-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QA] misleading message sent to client, when token_auth_enforced is true #41279
Comments
Hmm if OAuth is enabled you should not get to that screen. |
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. |
basic auth is unsupported? I still do most QA with basic auth.... 😱 |
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: For extra confusion, the server UI and docs mix up: app token, token, auth token, app password, app passcode. 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
The text was updated successfully, but these errors were encountered: