Choosing an integration method
Note:
This documentation has moved to a new home! Please update your bookmarks to the new URL for the up-to-date version of this page.
There are multiple mechanisms to join an Ubuntu system to an Active Directory tree (single domain) or a forest (multiple domains with trust relationships). It’s important to understand the features, pros, and cons, of each method, and cross reference those with what is the objective of the integration.
Three main criteria need to be evaluated:
- forest or single domain: Is the Active Directory deployment being joined composed of a single domain, or multiple domains (forest)?
- member server or workstation: Is the Ubuntu system that is being joined to Active Directory going to be a member server (it provides authentication and shares), or just a workstation/desktop which will not share files via the SMB protocol? If a workstation is also going to share files via SMB, then consider it a member server.
- Deterministic Linux ID: is it important that the same Active Directory user obtains the same Linux ID on all joined systems? For example, if NFS exports will be used between the joined systems.
| Requirement / Method | sssd | idmap_rid | idmap_autorid |
|---|---|---|---|
| Deterministic ID |  |
|
 |
| Undetermined ID | |
|
|
| Member server | |
|
|
| Not a member server | |
|
|
| AD multidomain (forest) | |
(*) |
|
| AD single domain | |
|
|
(*) The idmap_rid choice for multidomain Active Directory is doable, but with important caveats that are better explained in the Joining a forest with the rid backend howto.
Before going into the details of each integration method, it’s a good idea to familiarise yourself with the other basic concepts of Active Directory integration. These are shown next: