< Features
(Fix last update date) |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
The next major release of SSSD will include support for more advanced AD features for domain members. This includes site | The next major release of SSSD will include support for more advanced AD features for domain members. This includes support for site discovery, dynamic DNS updates, translating SIDs to names and dynamic discovery of the NetBIOS name of an AD domain. | ||
== Owner == | == Owner == | ||
| Line 34: | Line 34: | ||
* Site support: AD domains which include different physical locations can be split into sites. Each site represents a single physical location. With specially crafted DNS service record lookups an AD client can find the nearest domain controller, i.e. the domain controller in its site. This helps to keep network traffic local and allows clients to talk to the server with the lowest latency. | * Site support: AD domains which include different physical locations can be split into sites. Each site represents a single physical location. With specially crafted DNS service record lookups an AD client can find the nearest domain controller, i.e. the domain controller in its site. This helps to keep network traffic local and allows clients to talk to the server with the lowest latency. | ||
* DNS updates: AD clients will be able to update their DNS record dynamically if assigned a different IP address | * DNS updates: AD clients will be able to update their DNS record dynamically if assigned a different IP address | ||
* NetBIOS name discovery: at present, the NetBIOS name must be specified as the SSSD domain name in order to make it possible to look up users using the NetBIOS name. In F-19 the SSSD will enable to discover the NetBIOS name dynamically, allowing the lookups to just work. | * NetBIOS name discovery: at present, the NetBIOS name must be specified as the SSSD domain name in order to make it possible to look up users using the NetBIOS name. In F-19 the SSSD will enable to discover the NetBIOS name dynamically, allowing the lookups to just work. | ||
* An interface to translate SID identifiers to user or group names or POSIX ID. Such interface will be the basis of future CIFS integration as well as used directly by FreeIPA to provide a human-reasable representation of users and groups. | * An interface to translate SID identifiers to user or group names or POSIX ID. Such interface will be the basis of future CIFS integration as well as used directly by FreeIPA to provide a human-reasable representation of users and groups. | ||
Latest revision as of 20:53, 15 May 2013
SSSD improve AD integration
Summary
The next major release of SSSD will include support for more advanced AD features for domain members. This includes support for site discovery, dynamic DNS updates, translating SIDs to names and dynamic discovery of the NetBIOS name of an AD domain.
Owner
- Name: Jakub Hrozek
- Email: <jhrozek@redhat.com>
- Name: Sumit Bose
- Email: <sbose@redhat.com>
Current status
- Targeted release: Fedora 19
- Last updated: 2013-05-14
- Percentage of completion: 100%
- Subtasks finished in the Beta:
- DNS site discovery
- DNS dynamic updates
- Dynamic discovery of NetBIOS domain name
- An interface to translate SID to names or IDs and vice versa
Detailed Description
So far SSSD development of AD provider concentrated on doing the user and group lookups for the joined domain efficiently with high performance. With the next major release of SSSD support for some features which are specific to AD domain will be added. This includes:
- Site support: AD domains which include different physical locations can be split into sites. Each site represents a single physical location. With specially crafted DNS service record lookups an AD client can find the nearest domain controller, i.e. the domain controller in its site. This helps to keep network traffic local and allows clients to talk to the server with the lowest latency.
- DNS updates: AD clients will be able to update their DNS record dynamically if assigned a different IP address
- NetBIOS name discovery: at present, the NetBIOS name must be specified as the SSSD domain name in order to make it possible to look up users using the NetBIOS name. In F-19 the SSSD will enable to discover the NetBIOS name dynamically, allowing the lookups to just work.
- An interface to translate SID identifiers to user or group names or POSIX ID. Such interface will be the basis of future CIFS integration as well as used directly by FreeIPA to provide a human-reasable representation of users and groups.
Benefit to Fedora
With the improvements mentioned above a Fedora client which is joined to an AD domain and running SSSD has access to more advance features of the AD domain which were currently only available if winbind was used instead of SSSD.
Scope
All planned features for the next major release of SSSD can be found at [1]. The improvements mentioned above are tracked by the following tickets:
Links to design documents can be found in the tickets.
How To Test
Testing instructions can be found on the design documents in the SSSD wiki mentioned above. In the following a short summary for each feature can be found:
- Site support: instead of using a random DC form the AD domain, SSSD should only connect to DCs from the local site. This can be checked with the netstat or ss utilities.
- DNS updates: when the client address is changed, either manually or after DHCP assignment is changed, the client should automatically update its DNS record in the AD.
- Trusted domains: users and groups from the local forest and trusted forests should be available
- NetBIOS name discovery: it should be possible to request users using the NetBIOS domain name without specifying it manually in the config file.
- SID-to-Name interface: apart from testing the library itself or its Python bindings, this feature would be prominently visible using the FreeIPA server UI, where Windows users and groups could be identified with their real names (as opposed to SIDs)
There will be a Fedora Test day for this feature at 2013-05-09.
User Experience
The user might benefit from reduced latency while accessing the DC (site support) and the ability to use users and groups from trusted domains. Advanced features of the cifs-utils package, e.g. changing ACLs, do not require a running winbindd anymore but can be used with sssd as well.
Dependencies
No additional dependencies are expected. The required version if cifs-utils is already available in Fedora. To parse some blobs returned by AD some libraries from the samba-libs package are needed, but SSSD already depends on other samba libraries.
Contingency Plan
Not required, if some of the improvements are not available in time, they will be moved to the next release.
Documentation
For details see the design documents mentioned above.
Release Notes
With the latest major release to SSSD the integration into AD domain was improved. AD sites are respected and SSSD tries to access the nearest domain controller. users and groups from trusted domains are available. SSSD offers an ID mapping plugin for the cifs-utils which allows to use advanced features of cifs-utils with SSSD.