New issue
Advanced search Search tips

Issue 680503 link

Starred by 3 users
Status: Assigned
Owner:
rsorokin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
V2



Sign in to add a comment

Chromad: Make clear that we expect a sAMAccountName instead of a UPN

Project Member Reported by ljusten@chromium.org, Jan 12 2017 
Windows and kinit expect a sAMAccountName for login, not a user principal name. Reflect this in the UI.

Comment 1 by tnagel@chromium.org, Jan 31 2017

Summary: Chromad: Make clear that we expect a sAMAccountName instead of a UPN (was: authpolicy: Make clear that we expect a sAMAccountName instead of a UPN)
Forcing users to use a specific kind of id seems bad UX.  Can't we support both?

Comment 2 by rsorokin@chromium.org, Feb 17 2017 

We actually support both. But we need realm anyway.

Comment 3 by ljusten@chromium.org, Oct 18 2017

Labels: -M-58
►

Sign in to add a comment