Adding support for NIS clients
There are many scenarios in which adding the Centrify Network Information Service (adnisd) to your infrastructure can enable you to integrate Centrify and Active Directory with other enterprise solutions. For example, the adnisd Network Information Service and Centrify zones can be used to centrally manage and map multiple UNIX identities to a Windows user account for access resources stored on EMC Celerra Network Servers or Network Appliance Filers. Active Directory remains the central identity store and zones remain the primary way of mapping UNIX profiles to a user account, but the Centrify Network Information Service enables you to deliver the appropriate information to servers and devices across the network.
Using the Centrify Network Information Service in conjunction with the Centrify agent is a scenario like this provides the following advantages:
- Redundancy. As an NIS client, the Celerra Network Server can find NIS servers by broadcasting on the local subnet. If a subnet hosts more than one Centrify-managed computer acting as a NIS server, the Celerra or NetApp server can fail over from one NIS server to another NIS server on that subnet, thus enabling multiple NIS paths to the same data held within Active Directory.
- Multi-domain support. The Centrify NIS service can provide user mapping data to NIS clients who may have an account anywhere within an Active Directory forest, including remote or child domains. Through the Active Directory Global Catalog, Centrify agents can find user mapping information for users anywhere across the forest.
Extending your deployment with the Centrify Network Information Service also enables you to centrally manage network information and publish custom information to NIS clients throughout the network without modifying the underlying Active Directory schema.