HP UX Direry Server manual Tcp/Ip

Page 153

superuser

The most privileged user available on Unix machines. The superuser has complete access

 

privileges to all files on the machine. Also called root.

supplier

Server containing the master copy of directory trees or subtrees that are replicated to replica

 

servers.

supplier server

In the context of replication, a server that holds a replica that is copied to a different server is

 

called a supplier for that replica.

supplier-initiated

Replication configuration where supplier servers replicate directory data to any replica servers.

replication

 

symmetric

Encryption that uses the same key for both encrypting and decrypting. DES is an example of

encryption

a symmetric encryption algorithm.

system index

Cannot be deleted or modified as it is essential to Directory Server operations.

T

 

target

In the context of access control, the target identifies the directory information to which a

 

particular ACI applies.

target entry

The entries within the scope of a CoS.

TCP/IP

Transmission Control Protocol/Internet Protocol. The main network protocol for the Internet

 

and for enterprise (company) networks.

template entry

See CoS template entry.

time/date format

Indicates the customary formatting for times and dates in a specific region.

TLS

The new standard for secure socket layers; a public key based protocol. Also Transport Layer

 

Security.

topology

The way a directory tree is divided among physical servers and how these servers link with

 

one another.

Transport Layer

See TLS.

Security

 

U

 

uid

A unique number associated with each user on a Unix system.

URL

Uniform Resource Locater. The addressing system used by the server and the client to request

 

documents. It is often called a location. The format of a URL is

 

protocol://machine:port/document. The port number is necessary only on selected

 

servers, and it is often assigned by the server, freeing the user of having to place it in the URL.

V

 

virtual list view

Speeds up the display of entries in the Directory Server Console. Virtual list view indexes can

index

be created on any branch point in the directory tree to improve display performance.

 

See also browsing index.

X

 

X.500 standard

The set of ISO/ITU-T documents outlining the recommended information model, object classes

 

and attributes used by directory server implementation.

153

Page 152 Page 154
Image 153
Page 152 Page 154
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 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 classesMapping the data to the default schema Viewing the default directory schemaMatching data to schema elements 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 Deleting schema elements Creating custom schema filesStrategies for defining new attributes Naming schema files Custom schema best practicesUsing user defined as the origin Maintaining consistent schemaDefining schema in a single file Defining attributes before object classesSchema checking Maintaining consistency in replicated schemaSelecting consistent data formats 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 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 Introduction to replication Designing the replication processReplication concepts Unit of replicationRead-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 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 Designing synchronization Windows synchronization overviewSynchronization agreements 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 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 Designing a secure directory Unauthorized accessAbout security threats Unauthorized tamperingDenial of service Determining access rightsAnalyzing security needs 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 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 Grace login limit Password expirationPassword syntax checking Expiration warningPassword 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 TargetsAllowing or denying access Setting permissionsBind 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 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 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