-
Notifications
You must be signed in to change notification settings - Fork 770
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
Public Cert Auth fails, but only for Domain Accounts and only when using the sshd Service (as opposed to running sshd myself directly) #1213
Comments
In your case, it's having an issue turning your Domain\UserName into a user principal name. Can you confirm a user principal name is assigned for these accounts under the Account tab in Active Directory? Also, what OS is your domain controller running? |
@NoMoreFood That was it! I set the UPN attribute for zero\zeroadmin and it all worked. But the UPN attribute isn't mandatory...is there a different way that sshd can lookup the user in AD? (FYI, Domain Controller is Windows 2012 R2) |
@pldmgg Good to hear. @manojampalam Can you possibly check with any AD / Kerberos gurus to see if there is some of alternate format we can pass into ClientUpn for KERB_S4U_LOGON that will work for users that do not have their upn attribute defined in AD? I'm not sure if there's some sort of "default" upn that we should fallback to. Right now we're falling back to NetBiosDomain\SamAccountName which I think has zero chance of working for Kerberos S4U. |
@manojampalam Disregard previous request. Unbeknownst to me before now, apparently all accounts have an implicit UPN that defaults to SamAccountName@DnsDomainName; I have always explicitly set them in my forests. I will submit a pull request to try one and then the other. |
Pull request created: PowerShell/openssh-portable#332 |
@NoMoreFood Awesome! Thank you! |
Modified user principal name lookup to default to the implicit form (SamAccountName@DnsDomainName) if no explicit user principal name attribute is found on the account. PowerShell/Win32-OpenSSH#1213
Fixed in latest release |
…dress VS warnings. Includes: - Fix descriptor leaks in win32 fstat implementation: PowerShell/Win32-OpenSSH#1209 - Modified user principal name lookup to default to the implicit form (SamAccountName@DnsDomainName) if no explicit user principal name attribute is found on the account: PowerShell/Win32-OpenSSH#1213
EDIT : Just noticed that this issue (#1213) is a duplicate of #1177
The below version info applies to both Client (initiating ssh connection) and Server (Remote Host).
"OpenSSH for Windows" version
What is failing
Public Certificate Authentication is failing but ONLY for Domain Accounts and ONLY when running the sshd Service. In other words, Public Certificate Authentication DOES work when I run
sshd.exe -ddd
manually (i.e. NOT using the service), or if I use the sshd Service and connect with a Local User account on the Remote Host.Failure Output from SSHD Using SSHD Service When Connecting with Domain Account
Success Output from SSHD Using sshd -ddd When Connecting with Domain Account
The text was updated successfully, but these errors were encountered: