HP UX Direry Server manual Nis

Page 150

 

are automatically replicated to the other server. In case of conflict, a time stamp is used to

 

determine which server holds the most recent version.

multiplexor

The server containing the database link that communicates with the remote server.

N

 

n+1 directory

The problem of managing multiple instances of the same information in different directories,

problem

resulting in increased hardware and personnel costs.

name collisions

Multiple entries with the same distinguished name.

nested role

Allows the creation of roles that contain other roles.

network

Network Management Station component that graphically displays information about SNMP

management

managed devices, such as which device is up or down and which and how many error messages

application

were received.

network

See NMS.

management

 

station

 

NIS

Network Information Service. A system of programs and data files that Unix machines use to

 

collect, collate, and share specific information about machines, users, filesystems, and network

 

parameters throughout a network of computers.

NMS

Powerful workstation with one or more network management applications installed. Also

 

network management station.

ns-slapd

Red Hat's LDAP Directory Server daemon or service that is responsible for all actions of the

 

Directory Server.

 

See also slapd.

O

 

object class

Defines an entry type in the directory by defining which attributes are contained in the entry.

object identifier

A string, usually of decimal numbers, that uniquely identifies a schema element, such as an

 

object class or an attribute, in an object-oriented system. Object identifiers are assigned by ANSI,

 

IETF or similar organizations.

 

See also OID.

OID

See object identifier.

operational

Contains information used internally by the directory to keep track of modifications and subtree

attribute

properties. Operational attributes are not returned in response to a search unless explicitly

 

requested.

P

 

parent access

When granted, indicates that users have access to entries below their own in the directory tree

 

if the bind DN is the parent of the targeted entry.

pass-through

See PTA.

authentication

 

pass-through

In pass-through authentication, the PTA directory server will pass through bind requests to

subtree

the authenticating directory server from all clients whose DN is contained in this subtree.

password file

A file on Unix machines that stores Unix user login names, passwords, and user ID numbers.

 

It is also known as /etc/passwd because of where it is kept.

password policy

A set of rules that governs how passwords are used in a given directory.

PDU

Encoded messages which form the basis of data exchanges between SNMP devices. Also protocol

 

data unit.

permission

In the context of access control, permission states whether access to the directory information

 

is granted or denied and the level of access that is granted or denied.

 

See also access rights.

pointer CoS

A pointer CoS identifies the template entry using the template DN only.

150 Glossary

Page 149 Page 151
Image 150
Page 149 Page 151
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 corpDistributing directory data Directory design overviewAbout directory entries Performing queries on directory entriesDesign process outline Deploying the directoryOther general directory resources Page Information to include in the directory Planning the directory dataIntroduction to directory data 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 Standard schema Designing the directory schemaSchema design process overview 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 schemaNaming attributes and object classes When to extend the schemaGetting and assigning object identifiers 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 filesDefining schema in a single file Maintaining consistent schemaUsing user defined as the origin Defining attributes before object classesSchema checking Maintaining consistency in replicated schemaSelecting consistent data formats Other schema resources Designing the directory tree Designing the directory treeIntroduction to 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 Replication concepts Designing the replication processIntroduction to replication 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 siteReplication and Directory Server plug-ins Using replication with other Directory Server featuresReplication and access control Replication and database linksSchema replication See Creating custom schema files for more informationReplication and synchronization Designing synchronization Windows synchronization overviewSynchronization agreements Controlling synchronization Planning windows synchronizationChangelogs 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 About security threats Unauthorized accessDesigning a secure directory Unauthorized tamperingDenial of service Determining access rightsAnalyzing security needs Conducting regular audits Overview of security methodsEnsuring data privacy and integrity Example security needs analysisSelecting appropriate authentication methods Anonymous accessSimple password Simple authentication and security layer Certificate-based authenticationSimple password over SSL/TLS 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 syntax checking Password expirationGrace login limit 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 PermissionsBind rules Setting permissionsAllowing or denying access 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 resourcesDesign example a local enterprise Local enterprise schema designDirectory design examples 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