-
Notifications
You must be signed in to change notification settings - Fork 13
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
Issue: SSH login closes connection #665
Comments
That's weird. I don't see anything out of the ordinary in the logs you provided. Is anything printed to the terminal when the SSH connection is disconnected? Please also check if the journal on the server shows any relevant messages (for example by running |
Thank you for helping! On the client side (from WSL), all I get is:
When I run
The same happens after clearing the cache with: Is this an issue in the PAM perhaps? |
Yes, looks like PAM is incorrectly configured. Please paste the output of:
|
Other log that can help to see what's happening in PAM is Also installing |
My PAM config is as follows: /etc/pam.d/gdm-authd
/etc/pam.d/common-auth
/etc/pam.d/common-account
/etc/pam.d/common-password
In my
The |
Yeah, that's expected: Sadly we can't reliably support qr codes through SSH as most of clients don't support it (see #497 and #500), so depending on the UI we may show it or not for now. We've plans for using an |
Ah, I see. Thanks! I just found it curious that I suddenly saw it. Not sure what differs between SSH and |
So this is due to apparmor blocking access to authd socket when doing Now, looking at your pam configurations,
As per the |
If that works, go back to the default (by restoring the file or purging authd and installing it again), then modify diff --git a/debian/pam-configs/authd.in b/debian/pam-configs/authd.in
index 15528e92..808bbbda 100644
--- a/debian/pam-configs/authd.in
+++ b/debian/pam-configs/authd.in
@@ -5,7 +5,7 @@ Priority: 1050
Auth-Type: Primary
Auth:
[success=end ignore=ignore default=die] pam_authd_exec.so @AUTHD_DAEMONS_PATH@/authd-pam
-Account-Type: Additional
+Account-Type: Primary
Account:
[default=ignore success=ok user_unknown=ignore] pam_authd_exec.so @AUTHD_DAEMONS_PATH@/authd-pam
Password-Type: Primary
And run |
I figured :) ; but I forgot about the domain in my earlier tests...
This happens both for the original file, and when I change the line in the file you shared. Changing the I have reverted all these changes just to be sure. |
Do you get the same with actual ssh authentication too? As pam tester may still fail because of other reasons. |
I get the following error when using SSH (after changing
|
So, after a lot of headscratching, it turns out that my issue is caused by a case mismatch in PAM. When I use a lowercase username, I get the problems as described above, but when I use the casing that is used internally, everything seems to work... |
Yeah, that seems the case indeed. I won't close this as duplicate though, since I think we still have to fix the priority of the module as per #665 (comment) |
Is there an existing issue for this?
Describe the issue
I am running an Ubuntu 24.04.1 server for which I would like to allow SSO. I have followed the installation and configuration instructions in the Wiki, but I cannot log into the server. Whenever I have entered my local password, I get kicked out of the SSH connection. What am I missing?
Steps to reproduce
First SSH login:
Sequential SSH login:
System information and logs
authd version
authd-msentraid broker version
gnome-shell version
Distribution
Logs
authd broker configuration
/etc/authd/brokers.d/msentraid.conf
authd-msentraid configuration
Double check your logs
The text was updated successfully, but these errors were encountered: