HP UX Direry Server Multinational enterprise data design, Multinational enterprise schema design

Page 132

9.2.1 Multinational enterprise data design

Example Corp. International creates a deployment team to perform a site survey. The deployment team determines the following from the site survey:

•A messaging server is used to provide email routing, delivery, and reading services for most of Example Corp.'s sites. An enterprise server provides document publishing services. All servers run on Red Hat Enterprise Linux 5 (32-bit).

•Example Corp. needs to allow data to be managed locally. For example, the European site will be responsible for managing the Europe branch of the directory. This also means that Europe will be responsible for the master copy of its data.

•Because of the geographic distribution of Example Corp.'s offices, the directory needs to be available to users and applications 24 hours a day.

•Many of the data elements need to accommodate data values of several different languages.

NOTE:

All data use the UTF-8 characterset; any other characterset violates LDAP standards.

The deployment team also determines the following about the data design of the extranet:

•Parts suppliers need to log in to Example Corp.'s directory to manage their contracts with Example Corp. Parts suppliers depend on data elements used for authentication, such as name and user password.

•Example Corp.'s partners will use the directory to look up contact details of people in the partner network, such as email addresses and phone numbers.

9.2.2Multinational enterprise schema design

Example Corp. builds upon its original schema design by adding schema elements to support the extranet. Example Corp. adds two new objects, the exampleSupplier object class and the examplePartner object class.

The exampleSupplier object class allows one attribute, the exampleSupplierID attribute. This attribute contains the unique ID assigned by Example Corp. International to each automobile parts supplier with which it works.

The examplePartner object class allows one attribute, the examplePartnerID attribute. This attribute contains the unique ID assigned by Example Corp. International to each trade partner.

For information about customizing the default directory schema, see “Customizing the schema”.

9.2.3 Multinational enterprise directory tree design

Based on the expanded requirements, Example Corp. creates the following directory tree:

•The root of the directory tree is the dc=com suffix. Under this suffix, Example Corp. creates two branches. One branch, dc=exampleCorp, dc=com, contains data internal to Example Corp. International. The other branch, dc=exampleNet,dc=com, contains data for the extranet.

•The directory tree for the intranet (under dc=exampleCorp, dc=com) has three main branches, each corresponding to one of the regions where Example Corp. has offices. These branches are identified using the l (locality) attribute.

•Each main branch under dc=exampleCorp, dc=com mimics the original directory tree design of Example Corp. Under each locality, Example Corp. creates an ou=people, an ou=groups, an ou=roles, and an ou=resources branch. See Figure 9-1 “Directory tree for Example Corp.” for more information about this directory tree design.

132 Directory design examples

Page 131 Page 133
Image 132
Page 131 Page 133
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 Server plug-ins overview Overview of the basic directory treeDirectory Server data storage Expanded directory tree for example corpDirectory design overview About directory entriesDistributing directory data Performing queries on directory entriesDesign process outline Deploying the directoryOther general directory resources Page Planning the directory data Introduction to directory dataInformation to include in the directory Information to exclude from the directoryDefining directory needs Performing a site surveyIdentifying the applications that use the directory Identifying data sources Characterizing the directory dataDetermining level of service Considering a data masterDetermining data ownership Determining data access Example Tabulating data ownership and access Documenting the site surveyRepeating the site survey Page Designing the directory schema Schema design process overviewStandard schema Schema formatStandard attributes Standard object classes Syntaxes support in Directory ServerMapping the data to the default schema Viewing the default directory schemaMatching data to schema elements Customizing the schema Data mapped to default directory schemaWhen to extend the schema Getting and assigning object identifiersNaming attributes and object classes Strategies for defining new object classesNew object classes appear in LDAPv3 schema format as follows Deleting schema elements Creating custom schema filesStrategies for defining new attributes Custom schema best practices Naming schema filesMaintaining consistent schema Using user defined as the originDefining schema in a single file Defining attributes before object classesSchema checking Maintaining consistency in replicated schemaSelecting consistent data formats Other schema resources Designing the directory tree Introduction to the directory treeDesigning the directory tree Choosing a suffixSuffix naming conventions Naming multiple suffixesCreating the directory tree structure Branching the directoryIdentifying branch points Example environment directory treeDirectory tree for example isp Replication considerations Initial branching of the directory tree for example corpAccess control considerations Directory branching for example ispNaming Entries Naming person entriesNaming group entries Naming organization entriesGrouping directory entries About rolesNaming other kinds of entries About class of service Deciding between roles and groupsVirtual directory information tree views About virtual DIT views10 Examples of a flat and an organizationally-based DIT 11 a combined DIT using views Advantages of using virtual DIT views 12 a DIT with a virtual DIT view hierarchyExample of virtual DIT views Views and other directory features Effects of virtual views on performanceCompatibility with existing applications Directory tree design examples Directory tree for an international enterpriseOther directory tree resources Directory tree for an ISPPage Designing the directory topology Topology overviewDistributing the directory data About using multiple databases Storing suffix data in separate databasesAbout suffixes Directory tree spread across multiple databasesUsing referrals About knowledge referencesAbout default referrals Structure of an Ldap referralUsing smart referrals to redirect requests Smart referralsRedirecting a query to a different server and namespace Tips for designing smart referrals 10 a circular referral patternUsing chaining Deciding between referrals and chainingEvaluating access controls Usage differencesThis illustration, the following steps are performed Using indexes to improve database performance Overview of directory index typesEvaluating the costs of indexing Page Designing the replication process Introduction to replicationReplication concepts Unit of replicationRead-write and read-only replicas Suppliers and consumersReplication and changelogs Common replication scenarios Data consistencyReplication agreement Single-master replication Multi-master replicationMulti-master replication configuration two suppliers Multi-master replication configuration B four suppliers Cascading replication Replication traffic in a multi-master environmentCascading replication scenario Mixed environments Replication traffic and changelogs in cascading replicationDefining a replication strategy Combined multi-master and cascading replicationConducting a replication survey Replicated selected attributes with fractional replicationReplication resource requirements Managing disk space required for multi-master replicationUsing replication for high availability Replication across a wide-area networkUsing replication for local availability Using replication for load balancingExample of network load balancing Effects of replication and remote lookup on the networkExample of load balancing for improved performance Calculating Directory Server loadExample replication strategy for a small site Example replication strategy for a large siteUsing replication with other Directory Server features Replication and access controlReplication and Directory Server plug-ins Replication and database linksSchema replication See Creating custom schema files for more informationReplication and synchronization Designing synchronization Windows synchronization overviewSynchronization agreements Planning windows synchronization ChangelogsControlling synchronization Resource requirementsManaging disk space for the changelog Defining the connection typeDetermining the subtree to synchronize Interaction with a replicated environmentIdentifying the directory data to synchronize Multi-master Directory Server Windows domain synchronizationSynchronizing passwords and installing password services Defining an update strategyEditing the sync agreement NtUserDomainId Password policies Values for cn attributesValues for street and streetAddress Contraints on the initials attributeNtGroupId Name Unauthorized access Designing a secure directoryAbout security threats Unauthorized tamperingDenial of service Determining access rightsAnalyzing security needs Overview of security methods Ensuring data privacy and integrityConducting regular audits Example security needs analysisSelecting appropriate authentication methods Anonymous accessSimple password Certificate-based authentication Simple password over SSL/TLSSimple authentication and security layer Proxy authenticationPreventing 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 Password expiration Grace login limitPassword syntax checking Expiration warningPassword length Password minimum agePassword history Designing a password policy in a replicated environment Password storage schemesDesigning an account lockout policy Designing access control About the ACI formatTargets PermissionsSetting permissions Allowing or denying accessBind rules Precedence ruleWhen to deny access Where to place access control rulesUsing filtered access control rules Viewing ACIs Get effective rights Using ACIs Some hints and tricks Database encryption Use Ldap search filters cautiouslySecuring server to server connections Other security resourcesLocal enterprise schema design Directory design examplesDesign example a local enterprise Local enterprise data designLocal enterprise directory tree design Local enterprise topology design Database topologyLocal enterprise replication design Supplier architectureSupplier consumer architecture Supplier architecture for Example CorpLocal enterprise security design Supplier and consumer architecture for Example CorpLocal 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 Multinational enterprise topology design Directory tree for Example Corp. Internationals extranetServer topology 11 Server topology for Example Corp. Europe Multinational enterprise replication design 12 Server topology for Example Corp. Internationals extranet13 Supplier architecture for Example Corp. Europe Multinational enterprise security design Directory design examples Support and other resources Contacting HPRelated information HP-UX Directory Server administration server guide HP-UX documentation setTroubleshooting resources Typographic conventions144 Access rights GlossaryCGI 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