Open csware opened 4 years ago
er-vin
commented
4 years ago 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).
csware
commented
4 years ago 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.
csware
commented
4 years ago Some new findings:
When I add a new connection I see 0\authType=http and 0\http_user=XXX in %APPDATA%\Nextcloud\Nextcloud.cf and on my system where the issues arises authType is currently set to webflow.
What bothers me is that even if I manually change webflow to http the Nextcloud client automatically reverts to webflow. So this does not help, any idea why?
On my testmachine I can successfully logout and login again in the Nextcloud client.
csware
commented
4 years ago This issue only seems to occurr if at least one account with webflow is configured.
What does not work:
webflow to http in Nextcloud.cfgNextcloud_USERNAME:https://SERVERNAME/:1 (because the username needs to be empty, this cannot be done using the Windows UI)?!What does work, however, really evil:
Nextcloud.cfgNextcloud.cfgNextcloud.cfg, I always used the very same account w/o setting up any sync folders)Nextcloud.cfg and voilacsware
commented
4 years ago Easier fix:
Also, when I click on Logout and try to re-login again the authType is set to webflow again.
csware
commented
4 years ago er-vin
commented
4 years ago 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.
jangop
commented
4 years ago 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.
er-vin
commented
4 years ago 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.
jangop
commented
4 years ago 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.
er-vin
commented
4 years ago Yes, it is clearly misleading in that case. Still in that case it would go away if the root cause was handled.
hoehnp
commented
3 years ago sorry for bumping, but is there any activity in this issue? I think for students at German universities it would be very valuable.
paroj
commented
2 years ago I guess we could complete that by not migrating if the server version is too old.
that would be an improvement, as currently one needs to edit nextcloud.cfg after each restart..
ifrh
commented
1 year ago Did not work with Nextcloud client version 3.8.0, too.
Adding as new account after deleting the account, shows that the server is running Version 10.12.0.6.
ifrh
commented
1 year ago Did not work with Nextcloud client version 3.8.0, too.
Workaround, that is deleting authtype line from nextcloud.cfg, mentioned in June 2020 in https://github.com/nextcloud/desktop/issues/2111#issuecomment-647486747 , allows re-using SCIEBO-cloud between two starts of nextcloud client 3.8.0.
It seems to me, that setting authtype=webflow is not allowed for clients to communicate with SCIEBO-Server
bernd-wechner
commented
1 year ago 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.
[General]
clientVersion=3.10.0 (build 17672)
confirmExternalStorage=true
isVfsEnabled=false
logToTemporaryLogDir=true
newBigFolderSizeLimit=500
optionalDesktopNotifications=true
optionalServerNotifications=true
showInExplorerNavigationPane=true
updateSegment=45
useNewBigFolderSizeLimit=false
[Accounts]
version=2
[ActivityListHeader]
geometry=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x6\xfa\0\0\0\x5\x1\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x5\0\0\0\x81\0\0\0\x1\0\0\0\0\0\0\x4h\0\0\0\x1\0\0\0\0\0\0\x1M\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0`\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)
[LogBrowser]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x6\xb9\0\0\x3\xc1\0\0\n\xf0\0\0\x4\xf0\0\0\x6\xba\0\0\x3\xd7\0\0\n\xef\0\0\x4\xef\0\0\0\0\0\0\0\0\a\x80\0\0\x6\xba\0\0\x3\xd7\0\0\n\xef\0\0\x4\xef)
[Proxy]
type=2
[Settings]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x1\xbd\0\0\x1\xfa\0\0\b\xaa\0\0\x6$\0\0\x1\xbd\0\0\x2\x16\0\0\b\xaa\0\0\x6$\0\0\0\0\0\0\0\0\xf\0\0\0\x1\xbd\0\0\x2\x16\0\0\b\xaa\0\0\x6$)
[SharingDialog]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x6\x44\0\0\x3o\0\0\a\xc8\0\0\x4V\0\0\x6\x45\0\0\x3\x85\0\0\a\xc7\0\0\x4U\0\0\0\0\0\0\0\0\a\x80\0\0\x6\x45\0\0\x3\x85\0\0\a\xc7\0\0\x4U)
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.