-
Notifications
You must be signed in to change notification settings - Fork 774
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
Login in with the desktop client when using SSO (SAML with Keycloak) fails #1084
Comments
in our scenario, when we try to Login via NC DektopClient V2.51 and SSO & SAML, I get the SSO Authentication Login Screen for User and PW Input: After that we stuck with that screen |
@duckdiver that is another issue. your issue happens before the client wants to start to sync. Login works basically at our scenario. |
with NC Server V13 |
@lucode dont you stuck already in the first screen? |
No at the last one:
|
From my point of view you did mix up some configs about using token or password. |
No, |
Guys, any work around, i am facing this issue even i login successfully from IE. |
OS = centos 7.6.1810
|
Guys any clue? |
I got the log now:
Is on another server with NC 15.0.2 installed. |
For me it is working fine after disabling this option in SSO and SAML plugin
|
@mudasaryasin you are our hero, your suggestion works for us too. |
No me, it was discovered by my colleague. |
It is kind of a bug. But also a feature. The issue is that the old clients handled saml internally. Which often did 💥 and caused relogins to happen all the time. There is a bug somewhere in the saml detection logic. But I can't figure out where since I'm unable to reproduce it myself. |
+1 |
+3 |
seeing same with Mac Desktop Client: first the 302 redirect, then next request gets a "Method not allowed" 405:
NGINX is configured to allow PROPFIND waiting a few sec's actually Desktop Client seem to continue and is successfully logged in and starts syncing... it appears the initial login gets a 405 only. |
Same here, same fix worked. |
Hello everyone, |
We fixed it with the new login flow in 2.6. |
We run a Nectcloud instance on Hetzner and using Keycloak ID server witch allows SSO with SAML.
On the browser everything works great, but we can’t login into Nextcloud with the Desktop Client.
Android Client works too, but with the Desktop client the process stucks when I want to give Access to the files. We are not the only ones witch struggle with this issue:
https://help.nextcloud.com/t/issue-login-in-with-the-desktop-client-when-using-sso-saml-with-keycloak/47063
Expected behaviour
The Client should at this stage connect to the server an start synchronzing the files.
Actual behaviour
(https://help.nextcloud.com/uploads/default/original/2X/7/7675f215c2f638e02511e93f0d3ae79599a4d726.png)
The client shows then this state forever. The same siutation is when I using the app token instead of password. When I look in my settings I see there both Desktop and Android client are connected properly, so I assume the error is neither at the server or the Keycloak side. It must be a Desktop Client issue.
Steps to reproduce
Same issue on different machines (Win & Ubuntu)
Client configuration
Client version:
I have installed client Windows version: Version 2.5.1final (build 20181204).
And Ubuntu ppa version 2.5.1. It is the same issue.
Operating system:
Win 10
OS language:
German and EN
Installation path of client:
C:\Program Files (x86)\Nextcloud\nextcloud.exe
Server configuration
Hetzner Owncloud SaaS
Nextcloud version:
15.0.2
Logs
I don't get any logs, because the client is not yet running.
not accessible
No server logs
The text was updated successfully, but these errors were encountered: