Abstract:
A method of assigning the UNIX computers in a network to one of a plurality of groups called zones, of creating independent sets of UNIX identity information for each network entity (user or group) for separate zones, and of associating an entity&#39;s sets of UNIX entity information with a single global entity record for the entity in the network&#39;s identity resolver. A further method of allowing a UNIX computer to request entity information from the identity resolver, and of the identity resolver returning resolved entity information appropriate for the requesting computer&#39;s zone. A further method of managing sets of zone-specific UNIX identity information in the identity resolver to ensure that entity names and entity identification numbers are not duplicated within a zone and to all the same names and numbers to be duplicated across zones. Other embodiments are also described.

Description:
BRIEF DESCRIPTION OF THE INVENTION 
     Embodiments of this invention work with computers running UNIX (or a variation of UNIX) and an identity resolver (such as a directory server) within a network of computers. Embodiments of the invention allow the association of multiple sets of UNIX identity information (user or group names, user or group identification numbers, and similar data) with a single global entity record in an identity resolver database. When the user logs on to a UNIX computer, an embodiment of the invention selects the correct set of UNIX identity information based on the logical grouping of computers (called a zone) to which that UNIX computer belongs. The UNIX computer also uses the UNIX identity information at other times for identity lookup such as when the computer looks up the UNIX user name associated with a given UNIX user identification number. 
     BACKGROUND 
     Any network of UNIX computers relies on identity information to identify computer users and groups of computer users on the network. For example, when a user logs onto a network computer, he provides a user name to identify himself. Once the user is logged in, he is associated with a pre-assigned user identification number (UID) that is used within any computer on the network to identify that user. Files use UIDs to indicate file ownership, and UNIX operations use UIDs to report user activity. Other user identity information may specify the user&#39;s real name, the user&#39;s home directory, the type of shell he prefers to use, and the primary group of users to which he belongs. 
     Groups of users within a network likewise have identity information: a group name and an associated group identification number (GID). 
     Identity information is typically stored by an identity resolver (usually a directory server) attached to the network. The resolver stores the data in user records and group records, known collectively as entity records. The resolver may be an Active Directory (AD) server, a Lightweight Directory Access Protocol (LDAP) server, or other type of identity resolver such as a relational database. 
     Any computer can request identity information from the resolver by supplying an entity identifier (typically a user name, UID, group name, or GID). When a user logs on to a UNIX computer and supplies a user name, for example, the computer can request the UID, home directory, preferred shell, and principal group associated with that user name. Or a computer can ask the directory server to find the user name associated with the UID indicated as the owner of a file. 
     Entity identifiers used within a single network of UNIX computers must be unique for each entity within the network. If, for example, two users have the same user name, or if a single user name is associated with two different UIDs, then computers in the network cannot establish identity for a user name or UID. The same is true for group names and GIDs. 
     When a single UNIX network grows from scratch into a full network, entity name and ID duplication is generally not a problem. Each newly generated user name, UID, group name, and GID is checked against existing names and IDs to make sure it is not a duplicate. 
     Problems frequently arise, however, when two or more existing UNIX networks are linked together and their directories are consolidated into a single master directory for all networks. Because the original directories have developed names and IDs in ignorance of each other, it is not only possible but likely that they have used the same entity names and ID numbers. When the directories are consolidated, these identical names and IDs conflict, make user and group identity uncertain, and require that many user and group records be reassigned unique names and IDs. This creates a significant amount of work for system administrators and often confuses users who may be forced to use a new name for log-on. 
     SUMMARY OF THE INVENTION 
     Embodiments of this invention provide methods of creating multiple sets of UNIX identity information for each network entity, one information set for each group of UNIX computers (called a zone) in the network. Each of these information sets is a zone entity record. A zone entity record contains zone-specific information for an entity. That information identifies and defines the entity within a single zone of computers. For example, a zone entity record may contain UNIX identity information such as a UNIX user name, UID, preferred shell, primary group, and a home directory that identifies a user within a single zone. 
     An embodiment of the invention stores zone entity records in the identity resolver for the network. The embodiment also stores a set of global entity records there. A global entity record contains identity information that identifies an entity across all zones and any other computers in the network, including non-UNIX computers. A global entity record contains a global entity name and other identity information. A global user record, for example, contains a global user name that identifies a user throughout the entire network, and might also contain a password for the user, the user&#39;s real name, and other user information. 
     Embodiments of the invention associate all zone entity records for a single entity with the global entity record for the same entity. The identity resolver can use the associations in a global entity record to find zone entity records for an entity. For example, a directory server can find a global user record and examine an associated zone user record that contains UNIX identity information for the user within a particular zone. It is convenient to think of the global entity record as containing all its associated zone entity records, but these records need not be kept together physically in a single database. All that is necessary is that the zone data associated with a global entity record be accessible given a global entity identifier and a zone identifier, and vice versa: that a zone record contain enough information to locate its associated global record. 
     All the computers in a zone use a common set of user names, UIDs, group names, and GIDs. These identifiers are unique and non-conflicting within the zone. Computers in a second, different zone also use a common set of identity data for that second zone. However, identity data may conflict between zones. For example, the computers of a first zone may learn from the resolver that UID  504  identifies files and processes in the first zone that belong to John Doe, while the computers of a second zone may learn that the same UID,  504 , identifies files and processes in the second zone that belong to a different entity, Mary Smith. John Doe and Mary Smith will possess unique, non-conflicting global entity identifiers, but (as this example shows) they may be associated with conflicting zone entity records. 
     Embodiments of this invention also provide methods of dividing the UNIX computers in a network into one or more groups called zones. A single zone is specified for each UNIX computer. 
     The methods of an embodiment of this invention allow a UNIX computer in a network to make an identity query about an entity and receive resolved entity information that is appropriate for the entity within the computer&#39;s zone. The UNIX computer specifies an entity using an entity identifier (a user name or a UID, for example) in an identity query to the identity resolver. The query also communicates zone identity information from which the identity resolver can determine the querying computer&#39;s zone. 
     When the identity resolver receives an identity query from a UNIX computer in a zone, it locates a global entity record that corresponds to the query-specified entity, along with the zone entity records associated with the global entity record. The identity resolver then finds the zone entity record that corresponds to the inquiring computer&#39;s zone and returns resolved entity information that contains zone-specific information for the entity. That information will be appropriate for use on all computers that are members of the querying computer&#39;s zone. This type of identity query may occur, for example, when a UNIX computer performs a system lookup of a UID, user name, GID, or group name to determine identity information for a user or group in that zone. 
     An identity query may also occur during a user log-on, when the computer uses the supplied user name as an entity identifier in a query to find the appropriate global user record in a directory server and return the corresponding UID, home directory, preferred shell, and primary group for that user in the computer&#39;s zone. The methods of embodiments of this invention allow a user to log on to a computer by providing a zone user name that is specific to the zone or by providing a global user name that is recognized for all computers in the network. 
     The methods of this invention provide tools within the identity resolver to manage zone-specific information within each zone entity record. They allow duplicate entity names and entity identification numbers across different zones within the same network but prohibit duplication within each zone. The methods allow an administrator to restrict an entity&#39;s access to one or more zones by not providing zone entity records for those zones for the entity. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
       Embodiments of the invention are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.” 
         FIG. 1A  illustrates a computer network organized into zones in accordance with one embodiment of the invention. 
         FIG. 1B  illustrates how a user may log on to computers in different zones in the network defined in  FIG. 1A . 
         FIG. 2  illustrates a UNIX computer configured to operate in a zone in accordance with one embodiment of the invention. 
         FIG. 3  illustrates an identity resolver and workstation configured to supply resolved entity information to requesting computers in accordance with one embodiment of the invention. 
         FIG. 4  illustrates a global user record stored in an identity resolver with associated zone user records in accordance with one embodiment of the invention. 
         FIG. 5  illustrates a global group record stored in an identity resolver with associated zone group records in accordance with one embodiment of the invention. 
         FIG. 6A  illustrates a global user record associated with a single zone user record in accordance with one embodiment of the invention. 
         FIG. 6B  illustrates a global user record associated with an additional zone user record filled with default zone data in accordance with one embodiment of the invention. 
         FIG. 6C  illustrates a global user record with administrator-edited zone data in a zone user record accordance with one embodiment of the invention. 
         FIG. 7A  illustrates a global group record associated with two zone group records in accordance with one embodiment of the invention. 
         FIG. 7B  illustrates a global group record with an additional zone group record filled with default zone data in accordance with one embodiment of the invention. 
         FIG. 8  illustrates the process that occurs when a user attempts log-on through a UNIX computer in the network in accordance with one embodiment of the invention. 
         FIG. 9  illustrates the process that occurs when a process running on a UNIX computer requests a group information lookup from the identity resolver in accordance with one embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     This disclosure refers to UNIX user and group data at several levels of abstraction. For precision and ease of reference, Applicant provides the following definitions, which will be used throughout the specification and in the claims. 
     UNIX is defined to be the UNIX operating system, a UNIX-like operating system, or variants of the UNIX operating system such as the Linux operating system or the Macintosh OS X operating system. 
     Entity is defined to be either a user or a user group. 
     Identifier is either a name or an identification number that unambiguously identifies an entity. 
       FIG. 1A  illustrates a network of computers that may be operated in accordance with an embodiment of the invention. The network includes an identity resolver ( 20 ) in communication through a transmission channel ( 30 ) with a set of UNIX computers such as that specified by label ( 40 ). The computers in the network can number from several to a great number. 
     The identity resolver ( 20 ) can use any directory technology. This description uses Microsoft&#39;s Active Directory (AD) as an example, but the identity resolver might also be an LDAP server, a relational database, or other directory technology. The identity resolver can be a single server or a set of servers that supply unified identity resolution service to the network. 
     The transmission channel ( 30 ) can be any wired or wireless transmission channel. 
     The computers ( 40 ) in this network have each been assigned to a single zone such as Zone  1  shown by label ( 50 ). The number of zones in the network can range from one to as many zones as there are computers. In this example, Zone  1  includes computers A and B, Zone  2  includes computers C and D, and Zone  3  includes computers E, F, and G. 
       FIG. 1B  illustrates how a computer user ( 60 ) can log on to any UNIX computer in the network illustrated in  FIG. 1A . In this example, Alex Hsu logs on to computer B in Zone  1 , then later logs on to computer F in Zone  3  and later still into computer D in Zone  2 . At each log-on, the user must supply a user name to identify himself. That user name may be a zone-specific user name or a global user name. 
       FIG. 2  illustrates a UNIX computer ( 100 ) configured to operate in a zone. The computer is connected by the network&#39;s transmission channel ( 110 ) to the identity resolver ( 120 ). In this embodiment of the invention, the identity resolver contains a computer record ( 130 ) that stores information about the computer ( 100 ). The computer record contains zone configuration data ( 140 ) that specifies the zone to which the computer belongs. This zone configuration data ( 140 ) may also be stored in any other location accessible by the computer or identity resolver, whether it is on the computer itself or elsewhere in the network. 
     The computer contains zone logic ( 150 ) that is part of embodiments of the invention. The logic is used whenever a process running on the computer ( 100 ) requests user or group information from the identity resolver ( 120 ). This logic ( 150 ) consults the computer record ( 130 ) to determine the computer&#39;s zone, adds zone identity data to the request to identify the computer&#39;s zone, then sends the request to the identity resolver ( 120 ). The logic receives resolved entity information from the identity resolver in response. 
     Although the zone logic in this example resides on each UNIX computer, it does not have to reside there. It may also reside on the identity resolver where it determines a zone for a computer requesting identity information and then returns identity information appropriate for that zone. The resolver may determine the zone through an explicit zone identifier contained in a computer&#39;s request, or it may determine the zone through an implicit zone identifier accompanying the request. For example, an implicit zone identifier may be the Internet Protocol (IP) address, or another type of network address, of the requesting computer; or the method in which the request was received. The identity resolver can use the implicit zone identifier to determine the requesting computer&#39;s zone. 
       FIG. 3  illustrates an identity resolver ( 200 ) used to supply zone-specific entity information to requesting computers. The identity resolver is connected via the network&#39;s transmission channel ( 205 ) to other computers. 
     In this example, the identity resolver is a domain controller for Active Directory (AD), a Microsoft product that can provide directory information for both Windows and UNIX computers, but it might also be any directory server such as LDAP or a relational database. The identity resolver stores global entity records, zone entity records, and computer records on an accompanying database ( 210 ). The information stored by this particular embodiment of the invention for entity records is shown in  FIGS. 4 ,  5 , and  6 . 
     In this implementation, the identity resolver ( 200 ) used for the invention requires no special alterations or additions except for modified records. In other implementations of this invention, the zone logic that—in this implementation—resides on each UNIX computer in the network may reside instead on the identity resolver. 
     The identity resolver in this implementation is managed by an administrator ( 220 ) through a separate workstation ( 230 ) that is connected to the identity resolver via the network&#39;s transmission channel ( 205 ). This workstation provides the Active Directory Users and Computers console (ADUC) ( 240 ), a user interface that the administrator can use to manage records stored in the identity resolver. The workstation also provides a zone management console in the form of a snap-in component ( 250 ) for the Microsoft Management Console (MMC). The administrator can use this snap-in in as an alternative to the ADUC to managed stored records. The administrator can also use the MMC snap-in ( 250 ) to manage the zones themselves as described later. 
     The ADUC ( 240 ) has been customized with a set of zone extensions ( 260 ), a part of this invention that provides additional user interface controls to work with zone data within identity resolver records. The MMC snap-in ( 250 ) is a completely customized component, also a part of this embodiment, that provides the same additional user interface controls for working with zone data within identity resolver records. 
     Both the ADUC and the MMC snap-in work with zone record logic ( 270 ) installed on the workstation to help manage zone-specific information within records. The logic adds default zone-specific information to a zone entity record when requested. The logic also checks to ensure that when zone-specific information is added to a zone entity record that the entity name (user name or group name) and entity identification number (UID or GID) for the zone entity record are unique among all zone entity records affiliated with the same zone. 
     The MMC snap-in ( 250 ) supplies additional zone-management features. The snap-in displays the computers in each zone, reports on zone status, and allows an administrator ( 230 ) to create and remove zones and to set zone names. 
     The ADUC ( 240 ) and MMC snap-in ( 250 ) are just an example for this description. The administration console could just as well be one or more standard or custom consoles for any other identity resolution technology. To implement the methods of an embodiment of this invention, the console or consoles would be extended to handle zone-specific data within identity resolver records, to manage zones, and to ensure that entity names and entity identification numbers within a single zone are unique. 
       FIG. 4  shows a global user record ( 300 ) that is—in this example—an Active Directory user record. The global user record ( 300 ) is associated with zone user records ( 310 ) that contain additional zone-specific identity information. (This record could also be an LDAP record or any other standard record used by the identity resolver.) The zone user records ( 310 ) may be associated with the global user record ( 300 ) either by extending the existing global user record ( 300 ) if the identity resolver permits such extension or by other methods such as creating additional records or attaching external files. 
     The global user record ( 300 ) contains the global user name ( 320 ), which in this implementation is the user name provided in an Active Directory user record. The record contains other standard user record information ( 330 ) such as a password and a real user name that are typically stored in an Active Directory user record. The record is associated with a set of zone user records ( 310 ) that each contain the following information for a single zone in the network: a UNIX user name ( 340 ), a UID ( 350 ), the user&#39;s preferred shell ( 360 ), the user&#39;s home directory ( 370 ), and the name of the user&#39;s primary group ( 380 ). Each zone user record ( 310 ) may contain additional zone-specific information as well. 
     The zone user records ( 310 ) associated with the global user record ( 300 ) provide discrete sets of zone-specific information for the user in zero or more zones. In this example, there are zone entity records for zone  1  ( 390 ) and zone  2  ( 395 ). 
     If the global user record ( 300 ) is not associated with a zone user record ( 310 ) for a zone defined in the network, the user has no account in that zone and cannot log into a computer belonging to that zone. In this example, Alex Hsu&#39;s global user record is not associated with a zone user record for zone  3  and so he cannot log into that zone. 
     Adding zone user records ( 310 ) to an Active Directory record ( 300 ) in this implementation of the invention involves creating child instances of an object that defines zone user information. Each Active Directory user record contains one child instance for each zone user record. 
     Adding zone user records ( 310 ) to an LDAP record typically involves adding a multi-valued attribute to each LDAP user record. Each row in the attribute contains the information for a zone user record. 
     Adding zone user records ( 310 ) to a relational database typically involves creating a new table for each zone. Each table contains zone-specific data for all users enabled for a zone. The key to retrieving zone-specific data for a single user (which constitutes a zone user record) is the global user name and the zone identity information. The key for UID lookup is the UID and the zone identity information. 
       FIG. 5  shows a global group record ( 400 ) that is—in this example—an Active Directory group record. The global group record ( 400 ) is associated with zone group records ( 410 ) that contain additional zone-specific identity information. These zone group records ( 410 ) are associated with the global group record using the same methods described previously in the description of a global user record. (The global group record could also be an LDAP record or any other standard record used by the identity resolver.) 
     The global group record ( 400 ) contains the global group name ( 420 ), which in this implementation is the group name provided in an Active Directory directory group record. The global group record ( 400 ) contains other standard group record information ( 430 ). The record is associated with a set of zone group records ( 410 ) that each contain the following information for a single zone in the network: a UNIX group name ( 440 ) and a GID ( 450 ). Each zone group record ( 410 ) may contain additional zone-specific information as well. 
     If the global group record ( 400 ) is not associated with a zone group record ( 410 ) for a zone defined in the network, the group does not exist in that zone. In this example, there is no associated zone group record for zone  2  for this group, so the group does not exist in zone  2 . 
     Adding zone-specific data to a global group record uses the same techniques for AD, LDAP or an identity resolver as described for global user records in  FIG. 4 . 
       FIG. 6  illustrates the process that occurs when an administrator sets up a global user record ( 500 ) in the identity resolver to include a zone user record for a zone in the network. The global user record in this implementation is an Active Directory user record. The administrator begins by running the enhanced ADUC and finding an appropriate global user record ( 500 ), in this case for Alex Hsu of  FIG. 1 . Although this example uses the ADUC to work with a user record, other types of identity resolvers would supply an alternate form of record management. 
       FIG. 6A  shows the original global user record ( 500 ): the global user name ( 510 ) for the record is “alex.hsu@acme.com”. The administrator looks at the zone user records ( 520 ) associated with the global user record ( 500 ), and sees that Alex is enabled to log on to zone  2 , but not zone  3  or zone  1  because there are no zone user records for those zones. 
       FIG. 6B  shows the global user record after the administrator asks the enhanced ADUC to enable Alex Hsu for zone  1 . The ADUC creates a new zone user record for zone  1  ( 540 ), associates the new record with the global user record, and fills in default information in the zone user record for zone  1 . It also generates a UID ( 550 ) for the zone user record ( 540 ) and ensures that the UID ( 550 ) is unique within zone  1 . 
       FIG. 6C  shows the global user record after the administrator edits the default zone information in the new zone user record. If the administrator attempts to create a UNIX user name ( 560 ) or UID ( 550 ) that is not unique for the zone, the enhanced ADUC will not allow it. Once the administrator is finished and the modified record is stored, Alex Hsu is now enabled to log on and work in all the computers in zone  1 . Because there is no zone user record for zone  3  associated with the global user record, Hsu cannot log on to any computers in zone  3 . 
       FIG. 7  illustrates the process that occurs when an administrator sets up a global group record in the identity resolver to include information for a zone in the network. In this implementation, the global group record is an Active Directory group record. Although this example uses the ADUC to work with a group record, other types of identity resolvers would supply an alternate form of record management. 
       FIG. 7A  shows the global group record ( 600 ): the global group name ( 610 ) for the record is “operators”. The administrator looks at the zone group records associated with the global group record and finds them for zones  1  ( 620 ) and  2  ( 630 ) but not for zone  3 . This means that the group exists in zones  1  and  2 , but not in zone  3 . 
       FIG. 7B  shows the zone group records after the administrator asks the enhanced ADUC to enable the group for zone  3 . The ADUC creates a new zone group record ( 640 ) for zone  3 , attaches it to the global group record, generates a GID ( 650 ) for the zone that is unique within the zone, and uses the directory group name for the UNIX group name ( 660 ) within the zone group record after ensuring that the name is unique in the zone. 
       FIG. 8  illustrates the process that occurs when a user ( 700 ) attempts log-on through a UNIX computer ( 710 ) in the network. For this example, the user enters his UNIX user name ( 740 ) for zone  2 , of which the computer ( 710 ) is a member. In another case the user might enter his global user name instead. The UNIX user name in this example is “ahsu”. 
     The computer ( 710 ), while in the process of authenticating the log-on, executes its zone logic ( 720 ) to retrieve resolved entity information for the supplied UNIX user name ( 740 ). The zone logic ( 720 ) reads the zone configuration data and retrieves the name of its computer&#39;s zone ( 750 )—in this case, “zone  2 .” The logic ( 720 ) queries the identity resolver ( 730 ) for resolved entity information that is appropriate for the user in zone  2 . To do so, the logic ( 720 ) requests that the identity resolver ( 730 ) look through all UNIX user names specified in zone user records for zone  2  to find a match for the supplied UNIX user name ( 740 ) and, if that fails, to search for the supplied user name among all global user names—in other words, to search outside zone-specific UNIX user names. 
     If the identity resolver ( 730 ) finds a match either in zone  2  UNIX user names or in the global user names for all zones, it returns resolved entity information ( 760 ) from the global user record where the match was found. The resolved entity information ( 760 ) may include information necessary for user authentication. It may also include global user information and zone-specific information such as UID, home directory, preferred shell, and primary group. 
     If the user ( 700 ) had provided a global user name and the identity resolver ( 730 ) found a matching global user record but could not find a zone user record for zone  2 , then the look-up would have failed. 
     If the look-up succeeds, the zone logic ( 720 ) returns the information ( 760 ) to the computer ( 710 ), which can proceed with authentication and can use the resolved entity information as necessary for future interactions with the user. 
     Note that because the logic ( 720 ) looks for a user name ( 740 ) in both zone user records and in global user records, a user ( 700 ) may log on successfully using either his UNIX user name for the zone or his global user name. For example, Alex Hsu can log into a UNIX computer ( 710 ) in zone  2  using either his zone user name “ahsu” ( 740 ) or his global user name “alex.hsu@acme.com”. His UNIX user name ( 740 ) is not guaranteed to work in other zones, because he might have different UNIX user names defined in those zones. His global user name, however, will work for log-on in any zone in which he is enabled. 
       FIG. 9  illustrates the actions that occur when a process ( 800 ) running on a UNIX computer requests a group information lookup from the identity resolver ( 830 ). The process supplies a GID number ( 840 ) and requests the corresponding group name from the UNIX operating system ( 810 ). The UNIX OS executes the zone logic ( 820 ), which looks up the computer&#39;s zone in the zone configuration data, finds “zone  1 ”, then queries the identity resolver ( 830 ) to find any zone group record specifying the GID  11000  ( 840 ) for zone  1 . 
     The identity resolver ( 830 ) finds the GID in a zone group record associated with a global group record using the global group name “operators”. The identity resolver ( 830 ) looks up the UNIX group name ( 850 ) in the associated zone record for zone  1 , finds “staff”, and returns that name to the zone logic ( 820 ). The zone logic ( 820 ) returns “staff” to the UNIX OS ( 810 ), which returns it to the requesting process ( 800 ). 
     The foregoing description of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents. 
     An embodiment of the invention may be a machine-readable medium having stored thereon instructions which cause a processor to perform operations as described above. In other embodiments, the operations might be performed by specific hardware components that contain hardwired logic. Those operations might alternatively be performed by any combination of programmed computer components and custom hardware components. 
     A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), not limited to Compact Disc Read-Only Memory (CD-ROMs), Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), and a transmission over the Internet.