HP UX Direry Server manual Creating the directory tree structure, Branching the directory

Page 41

The databases could be stored on a single server or multiple servers depending on resource constraints.

4.2.2 Creating the directory tree structure

Decide whether to use a flat or a hierarchical tree structure. As a general rule, try to make the directory tree as flat as possible. However, a certain amount of hierarchy can be important later when information is partitioned across multiple databases, prepare replication, and set access controls.

The structure of the tree involves the following steps and considerations:

•“Branching the directory”

•“Identifying branch points”

•“Replication considerations”

•“Access control considerations”

4.2.2.1Branching the directory

Design the hierarchy to avoid problematic name changes. The flatter a namespace is, the less likely the names are to change. The likelihood of a name changing is roughly proportional to the number of components in the name that can potentially change. The more hierarchical the directory tree, the more components in the names, and the more likely the names are to change.

Following are some guidelines for designing the directory tree hierarchy:

•Branch the tree to represent only the largest organizational subdivisions in the enterprise.

Any such branch points should be limited to divisions (Corporate Information Services, Customer Support, Sales and Professional Services, and so forth). Make sure that the divisions used to branch the directory tree are stable; do not perform this kind of branching if the enterprise reorganizes frequently.

•Use functional or generic names rather than actual organizational names for the branch points.

Names change, and it is really bad to have to change the directory tree every time the enterprise renames its divisions. Instead, use generic names that represent the function of the organization (for example, use Engineering instead of Widget Research and Development).

•If there are multiple organizations that perform similar functions, try creating a single branch point for that function instead of branching based along divisional lines.

For example, even if there are multiple marketing organizations, each of which is responsible for a specific product line, create a single ou=Marketing subtree. All marketing entries then belong to that tree.

Branching in an enterprise environment Name changes can be avoided if the directory tree structure is based on information that is not likely to change. For example, base the structure on types of objects in the tree rather than organizations. This helps avoid shuffling an entry between organizational units, which requires modifying the distinguished name (DN), which is an expensive operation.

There are a handful of common objects that are good to use to define the structure:

•ou=people

•ou=groups

•ou=services

A directory tree organized using these objects might appear as shown below.

4.2 Designing the directory tree

41

Page 40 Page 42
Image 41
Page 40 Page 42
Contents HP-UX Directory Server deployment guide Page Table of Contents Designing the directory tree Designing the replication process 103 145 125141 155 About global directory services Introduction to directory servicesAbout directory services Overview of the server frontend Introduction to Directory ServerAbout Ldap Overview of the basic directory tree Server plug-ins overviewExpanded directory tree for example corp Directory Server data storageAbout directory entries Directory design overviewDistributing directory data Performing queries on directory entriesDeploying the directory Design process outlineOther general directory resources Page Introduction to directory data Planning the directory dataInformation to include in the directory Information to exclude from the directoryPerforming a site survey Defining directory needsIdentifying the applications that use the directory Characterizing the directory data Identifying data sourcesConsidering a data master Determining level of serviceDetermining data ownership Determining data access Documenting the site survey Example Tabulating data ownership and accessRepeating the site survey Page Schema design process overview Designing the directory schemaStandard schema Schema formatStandard attributes Syntaxes support in Directory Server Standard object classesMatching data to schema elements Mapping the data to the default schemaViewing the default directory schema Data mapped to default directory schema Customizing the schemaGetting and assigning object identifiers When to extend the schemaNaming attributes and object classes Strategies for defining new object classesNew object classes appear in LDAPv3 schema format as follows Strategies for defining new attributes Deleting schema elementsCreating custom schema files Naming schema files Custom schema best practicesUsing user defined as the origin Maintaining consistent schemaDefining schema in a single file Defining attributes before object classesSelecting consistent data formats Schema checkingMaintaining consistency in replicated schema Other schema resources Introduction to the directory tree Designing the directory treeDesigning the directory tree Choosing a suffixNaming multiple suffixes Suffix naming conventionsBranching the directory Creating the directory tree structureExample environment directory tree Identifying branch pointsDirectory tree for example isp Initial branching of the directory tree for example corp Replication considerationsDirectory branching for example isp Access control considerationsNaming person entries Naming EntriesNaming organization entries Naming group entriesNaming other kinds of entries Grouping directory entriesAbout roles Deciding between roles and groups About class of serviceAbout virtual DIT views Virtual directory information tree views10 Examples of a flat and an organizationally-based DIT 11 a combined DIT using views 12 a DIT with a virtual DIT view hierarchy Advantages of using virtual DIT viewsExample of virtual DIT views Compatibility with existing applications Views and other directory featuresEffects of virtual views on performance Directory tree for an international enterprise Directory tree design examplesDirectory tree for an ISP Other directory tree resourcesPage Distributing the directory data Designing the directory topologyTopology overview Storing suffix data in separate databases About using multiple databasesDirectory tree spread across multiple databases About suffixesAbout knowledge references Using referralsStructure of an Ldap referral About default referralsSmart referrals Using smart referrals to redirect requestsRedirecting a query to a different server and namespace 10 a circular referral pattern Tips for designing smart referralsDeciding between referrals and chaining Using chainingUsage differences Evaluating access controlsThis illustration, the following steps are performed Overview of directory index types Using indexes to improve database performanceEvaluating the costs of indexing Page Introduction to replication Designing the replication processReplication concepts Unit of replicationReplication and changelogs Read-write and read-only replicasSuppliers and consumers Replication agreement Common replication scenariosData consistency Multi-master replication Single-master replicationMulti-master replication configuration two suppliers Multi-master replication configuration B four suppliers Replication traffic in a multi-master environment Cascading replicationCascading replication scenario Replication traffic and changelogs in cascading replication Mixed environmentsCombined multi-master and cascading replication Defining a replication strategyReplicated selected attributes with fractional replication Conducting a replication surveyManaging disk space required for multi-master replication Replication resource requirementsReplication across a wide-area network Using replication for high availabilityUsing replication for load balancing Using replication for local availabilityEffects of replication and remote lookup on the network Example of network load balancingCalculating Directory Server load Example of load balancing for improved performanceExample replication strategy for a large site Example replication strategy for a small siteReplication and access control Using replication with other Directory Server featuresReplication and Directory Server plug-ins Replication and database linksSee Creating custom schema files for more information Schema replicationReplication and synchronization Synchronization agreements Designing synchronizationWindows synchronization overview Changelogs Planning windows synchronizationControlling synchronization Resource requirementsDefining the connection type Managing disk space for the changelogInteraction with a replicated environment Determining the subtree to synchronizeMulti-master Directory Server Windows domain synchronization Identifying the directory data to synchronizeEditing the sync agreement Synchronizing passwords and installing password servicesDefining an update strategy NtUserDomainId Values for cn attributes Password policiesContraints on the initials attribute Values for street and streetAddressNtGroupId Name Designing a secure directory Unauthorized accessAbout security threats Unauthorized tamperingAnalyzing security needs Denial of serviceDetermining access rights Ensuring data privacy and integrity Overview of security methodsConducting regular audits Example security needs analysisAnonymous access Selecting appropriate authentication methodsSimple password Simple password over SSL/TLS Certificate-based authenticationSimple authentication and security layer Proxy authenticationHow password policy works Preventing authentication by account deactivationDesigning a password policy Designing a secure directory Designing a password policy Password policy checking process User-defined passwords Password policy attributesPassword change after reset Grace login limit Password expirationPassword syntax checking Expiration warningPassword history Password lengthPassword minimum age Designing an account lockout policy Designing a password policy in a replicated environmentPassword storage schemes About the ACI format Designing access controlPermissions TargetsAllowing or denying access Setting permissionsBind rules Precedence ruleUsing filtered access control rules When to deny accessWhere to place access control rules Viewing ACIs Get effective rights Using ACIs Some hints and tricks Use Ldap search filters cautiously Database encryptionOther security resources Securing server to server connectionsDirectory design examples Local enterprise schema designDesign example a local enterprise Local enterprise data designLocal enterprise directory tree design Database topology Local enterprise topology designSupplier architecture Local enterprise replication designSupplier architecture for Example Corp Supplier consumer architectureSupplier and consumer architecture for Example Corp Local enterprise security designLocal enterprise operations decisions Local enterprise tuning and optimizationsDesign example a multinational enterprise and its extranet Multinational enterprise directory tree design Multinational enterprise schema designMultinational enterprise data design Entry for the l=Asia entry appears in Ldif as follows Directory tree for Example Corp. Internationals extranet Multinational enterprise topology designServer topology 11 Server topology for Example Corp. Europe 12 Server topology for Example Corp. Internationals extranet Multinational enterprise replication design13 Supplier architecture for Example Corp. Europe Multinational enterprise security design Directory design examples Related information Support and other resourcesContacting HP HP-UX documentation set HP-UX Directory Server administration server guideTypographic conventions Troubleshooting resources144 Glossary Access rightsCGI DIT GSS-API Ldap NIS PTA Sasl TCP/IP 154 Index Index OID Sasl 159
Related manuals
Manual 96 pages 26.31 Kb Manual 68 pages 26.36 Kb Manual 18 pages 3.79 Kb Manual 72 pages 14.95 Kb

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.
Top Page Image Contents