-
Notifications
You must be signed in to change notification settings - Fork 812
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
Re-Login doesn't work with (old) ownCloud servers #2111
Comments
I suspect that's because your very old ownCloud instance doesn't support the new login flow... even the ownCloud client stopped supporting it. I doubt much can be done about that. For the time being you could try to make you own build of the client with shibboleth support but that code will be canned soon (has its own implication on install payload and so on). |
When I connect to the very same ownCloud instance using "Add account" it still works. That's the reason why I consider this a regression. |
Some new findings: What bothers me is that even if I manually change On my testmachine I can successfully logout and login again in the Nextcloud client. |
This issue only seems to occurr if at least one account with What does not work:
What does work, however, really evil:
|
Easier fix:
Also, when I click on Logout and try to re-login again the authType is set to |
I see now I understand better. Indeed it looks related to the migration you spotted... I guess we could complete that by not migrating if the server version is too old. Would have to look for which versions of both servers support webflow or not. Indeed we really only have the version and not the server type. |
Should I open an additional issue for “Open browser again” and “Copy link” being unresponsive, or it that considered part of this issue? @er-vin To clarify. Clicking either of the two options brings up a note “Starting authorization...” that stays on screen for but a moment, but then nothing happens. This also means that no “link” is being copied: Btw, this issue is related to #1915. |
I don't think a new ticket is needed for this. It's pretty much due to the Bad Request so there's nothing to open or copy in such a case. |
I agree. However, the interface is mishandling the communication of said request with regards to the user. A buttons that does nothing is a bug in its own right. |
Yes, it is clearly misleading in that case. Still in that case it would go away if the root cause was handled. |
sorry for bumping, but is there any activity in this issue? I think for students at German universities it would be very valuable. |
that would be an improvement, as currently one needs to edit nextcloud.cfg after each restart.. |
Workaround, that is deleting It seems to me, that setting |
I'm getting this message too on a virgin install of Nextcloud 27, and newly downloaded desktop client (appImage) "Could not parse the JSON returned from the server: illegal value" here is my nextcloud.cfg, no account info at all or authtype.
|
Expected behaviour
I use the Nextcloud Client to sync with my nextcloud instance and onother old owncloud instance.
Recently the app token for the owncloud instance was revoked or got lost. Not I cannot log in again to that instance.
I expect that a dialog opens where I can enter my credentials (the very same dialog which appears when I add a new account for an old owncloud server).
Actual behaviour
When I click on Log-in I get a dialog where I see the error "Error acceccing the token endpoint: ... server replied: Precondition failed". Below there are two options "Open browser again" and "Copy link", both are not working.
When I try to add another account for that server I am correctly asked for my credentials by the nextcloud client.
How can I log in to that account again? (even very hacky methods are welcome)
Steps to reproduce
Client configuration
Client version: 2.6.4stable-Win64 (build 20200303)
Operating system: Win10 1909 x64
OS language: German
Server configuration
Owncloud version: 9.1.6 (stable) (yes, that'S very old, but not under my control)
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
The text was updated successfully, but these errors were encountered: