Can't login using Administrator account |
||||
Issue descriptionWhat exactly is the cause of that problem and how can it be fixed?
,
Jan 12 2017
Windows logon and kinit prefer a sAMAccountName, probably for backwards compatibility. UPN is only optional. Change authpolicy to prefer sAMAccountName as well.
,
Jan 13 2017
,
Jan 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/6d006a0b3c23fa5dc033f01d13f3c4c1bade2556 commit 6d006a0b3c23fa5dc033f01d13f3c4c1bade2556 Author: Lutz Justen <ljusten@chromium.org> Date: Thu Jan 12 14:15:48 2017 authpolicy: Prefer sAMAccountName for objectGUID search Use sAMAccountName for searching for the objectGUID/account id and fall back to userPrincipalName. This is what Windows and kinit seem to do, i.e. if you kinit name@realm.com, it assumes that name is a sAMAccountName first and only if there is no such sAMAccountName, it assumes it's a UPN. BUG= chromium:680454 TEST=Emerges, tested both cases with and without fallback. Change-Id: Ic05f8b46e8f33b04c21a8d722ab6db27b007b31c Reviewed-on: https://chromium-review.googlesource.com/427680 Commit-Ready: Lutz Justen <ljusten@chromium.org> Tested-by: Lutz Justen <ljusten@chromium.org> Reviewed-by: Roman Sorokin <rsorokin@chromium.org> [modify] https://crrev.com/6d006a0b3c23fa5dc033f01d13f3c4c1bade2556/authpolicy/samba_interface.cc
,
Jan 13 2017
,
Jul 6 2017
bulk Verify of older or not-user-facing Chromad bugs |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsorokin@chromium.org
, Jan 12 2017Owner: ljusten@chromium.org
Status: Assigned (was: Available)