Loading...
Loading...
AD domain users receive "Access Denied" when attempting SSH/CLI login after upgrading to OneFS 9.13.1.1 GUI login works correctly with the same AD credentials Local user SSH login is unaffected Auth.log shows errors like: error: check_pam_user: PAM user "DOMAIN\\user" does not match previous "domain\\user" Auth.log shows: error: PAM: Unknown user for domain\\user from X.X.X.X Auth.log shows errors such as: PAM user "EXAMPLE\Administrator" does not match previous "administrator@example.com" UPN format SSH logins do not work, the same errors are showing in the logs.
OneFS 9.13.1.1 performs case-sensitive username comparison. PAM canonicalizes AD usernames (e.g., "domain\user" → "DOMAIN\user" ), so the case-sensitive check rejects domain users whose login name was typed in lower-case. This is a defect and is being worked on by OneFS Engineering.
Workaround: AD users must match the case exactly when entering their username (e.g., use "DOMAIN\username" instead of "domain\username" ). UPN format ( user@domain ) logins have no other workaround other than switching to "DOMAIN\username" format. If using a single-slash between the domain and username, remember to place the entire string in double-quotes (i.e. "DOMAIN\username" instead of just DOMAIN\username ). Alternatively, no quotes with two slashes (i.e. DOMAIN\\username ) may also work. If the fix for the case-sensitivity issue is not installed then the case must match AD. A fix for this is being targeted for OneFS 9.13.1.3 subject to change. The KB will be updated when more information is available.
Click on a version to see all relevant bugs