UW NetID Integration with Windows
There are many options for using UWNetIDs and
"centrally" maintained passwords with Windows. However,
where possible we recommend using the UW Windows
Infrastructure (UWWI).
The most common options are summarized with further details given
below.
Summaries
-
UW Windows Infrastructure via delegated OU
- Windows account has a UW NetID password.
- Only requires a delegated OU
- No user confusion
- Authorization groups tied to UWWI user accounts
that are auto-provisioned from institutional data.
These include groups based on affiliations (e.g.
student, staff, faculty), and course groups.
-
UW Windows Infrastructure
via trust
- Windows account has UW NetID password.
- Requires a trust to UWWI and your own Windows domain.
- Users might need to use both the UWWI user account and your
local domain account.
- Authorization groups tied to UWWI user accounts
that are auto-provisioned from institutional data.
These include groups based on affiliations (e.g.
student, staff, faculty), and course groups.
-
Kerberos realm trust option
- Authentication won't work for ALL
services.
- Users have two DISTINCT accounts and passwords
(local domain and UW NetID, but only need to know
about their UW NetID.
- Requires you to provision an account for each user in your local
domain.