HP UX Direry Server manual Examples of a flat and an organizationally-based DIT

Page 51

Figure 4-10 Examples of a flat and an organizationally-based DIT

Using a hierarchical DIT, a deployment must then determine the subject domain of the hierarchy. Only one choice can be made; the natural tendency is to choose the organizational hierarchy.

This view of the organization serves well in many cases, but having only a single view can be very limiting for directory navigation and management. For example, an organizational hierarchy is fine for looking for entries that belong to people in the Accounts department. However, this view is much less useful for finding entries that belong to people in a geographical location, such as Mountain View, California. The second query is as valid as the first, yet it requires knowledge of the attributes contained in the entries and additional search tools. For such a case, navigation via the DIT is not an option.

Similarly, management of the directory is much easier when the DIT matches the requirements of the management function. The organization of the DIT may also be affected by other factors, such as replication and migration considerations, that cause the DIT to have functional utility for those applications but very little practical utility in other cases.

From the above discussion, it is clear that hierarchies are a useful mechanism for navigation and management. To avoid the burden of making changes to an existing DIT, however, a deployment may elect to forgo a hierarchy altogether in favor of a flat DIT.

It would be advantageous for deployments if the directory provided a way to create an arbitrary number of hierarchies that get mapped to entries without having to move the target entries in question. The virtual DIT views feature of Directory Server resolves the quandary of deciding the type of DIT to use for the directory deployment.

Virtual DIT views provide a way to hierarchically navigate entries without the requirement that those entries physically exist in any particular place. The virtual DIT view uses information about the entries to place them in the view hierarchy. To client applications, virtual DIT views appear as ordinary container hierarchies. In a sense, virtual DIT views superimpose a DIT hierarchy over a set of entries, irrespective of whether those entries are in a flat namespace or in another hierarchy of their own.

Create a virtual DIT view hierarchy in the same way as a normal DIT hierarchy. Create the same entries (for example, organizational unit entries) but with an additional object class (nsview) and a filter attribute (nsviewfilter) that describes the view. After adding the additional attribute, the entries that match the view filter instantly populate the view. The target entries only appear to exist in the view; their true location never changes. Virtual DIT views behave like normal DITs in that a subtree or a one-level search can be performed with the expected results being returned.

For information about adding and modifying entries, refer to "Creating Directory Entries" in the HP-UX Directory Server administrator guide

4.4 Virtual directory information tree views

51

Page 50 Page 52
Image 51
Page 50 Page 52
Contents HP-UX Directory Server deployment guide Page Table of Contents Designing the directory tree Designing the replication process 103 125 141145 155 Introduction to directory services About directory servicesAbout global directory services Introduction to Directory Server About LdapOverview of the server frontend Overview of the basic directory tree Server plug-ins overviewExpanded directory tree for example corp Directory Server data storagePerforming queries on directory entries Directory design overviewAbout directory entries Distributing directory dataDeploying the directory Design process outlineOther general directory resources Page Information to exclude from the directory Planning the directory dataIntroduction to directory data Information to include in 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 format Designing the directory schemaSchema design process overview Standard schemaStandard attributes Syntaxes support in Directory Server Standard object classesMapping the data to the default schema Viewing the default directory schemaMatching data to schema elements Data mapped to default directory schema Customizing the schemaStrategies for defining new object classes When to extend the schemaGetting and assigning object identifiers Naming attributes and object classesNew object classes appear in LDAPv3 schema format as follows Deleting schema elements Creating custom schema filesStrategies for defining new attributes Naming schema files Custom schema best practicesDefining attributes before object classes Maintaining consistent schemaUsing user defined as the origin Defining schema in a single fileSchema checking Maintaining consistency in replicated schemaSelecting consistent data formats Other schema resources Choosing a suffix Designing the directory treeIntroduction to the directory tree Designing the directory treeNaming 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 entriesGrouping directory entries About rolesNaming other kinds of entries 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 Views and other directory features Effects of virtual views on performanceCompatibility with existing applications Directory tree for an international enterprise Directory tree design examplesDirectory tree for an ISP Other directory tree resourcesPage Designing the directory topology Topology overviewDistributing the directory data 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 Unit of replication Designing the replication processIntroduction to replication Replication conceptsRead-write and read-only replicas Suppliers and consumersReplication and changelogs Common replication scenarios Data consistencyReplication agreement 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 database links Using replication with other Directory Server featuresReplication and access control Replication and Directory Server plug-insSee Creating custom schema files for more information Schema replicationReplication and synchronization Designing synchronization Windows synchronization overviewSynchronization agreements Resource requirements Planning windows synchronizationChangelogs Controlling synchronizationDefining 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 synchronizeSynchronizing passwords and installing password services Defining an update strategyEditing the sync agreement NtUserDomainId Values for cn attributes Password policiesContraints on the initials attribute Values for street and streetAddressNtGroupId Name Unauthorized tampering Unauthorized accessDesigning a secure directory About security threatsDenial of service Determining access rightsAnalyzing security needs Example security needs analysis Overview of security methodsEnsuring data privacy and integrity Conducting regular auditsAnonymous access Selecting appropriate authentication methodsSimple password Proxy authentication Certificate-based authenticationSimple password over SSL/TLS Simple authentication and security layerPreventing authentication by account deactivation Designing a password policyHow password policy works Designing a secure directory Designing a password policy Password policy checking process Password policy attributes Password change after resetUser-defined passwords Expiration warning Password expirationGrace login limit Password syntax checkingPassword length Password minimum agePassword history Designing a password policy in a replicated environment Password storage schemesDesigning an account lockout policy About the ACI format Designing access controlPermissions TargetsPrecedence rule Setting permissionsAllowing or denying access Bind rulesWhen to deny access Where to place access control rulesUsing filtered 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 connectionsLocal enterprise data design Local enterprise schema designDirectory design examples Design example a local enterpriseLocal 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 tuning and optimizations Design example a multinational enterprise and its extranetLocal enterprise operations decisions Multinational enterprise schema design Multinational enterprise data designMultinational enterprise directory tree 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 Support and other resources Contacting HPRelated information 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