Red Hat Directory Server B.08.00.01 for HP-UX Release Notes and Supplemental Instructions HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 HP Part Number: 5900-1046 Published: August 2010 Edition: 3.
© Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Important Licensing Requirements IMPORTANT: Red Hat Directory Server product licensing requirements have been changed. Please read the following licensing terms and conditions.
Table of Contents 1 Release Notes for Red Hat Directory Server B.08.00................................................9 1.1 What is new with this release (B.08.00.01) of Red Hat Directory Server..........................................9 1.2 New Features in Red Hat Directory Server 8.0.................................................................................9 1.3 Differences Between Red Hat Directory Server 7.1 and Red Hat Directory Server 8.0..................11 1.4 Documentation....................
4 Supplemental Information for Administering Red Hat Directory Server 8.0..........33 4.1 Stopping and Restarting the Directory Server................................................................................33 4.2 Stopping and Restarting the Administration Server.......................................................................33 4.3 Tips for Using Red Hat Directory Server 8.0...................................................................................33 4.3.1 Importing LDIF Files.........
A Migration Tools............................................................................................................59 A.1 Major Options.................................................................................................................................59 A.2 Arguments......................................................................................................................................60 B Schema Changes....................................................................
1 Release Notes for Red Hat Directory Server B.08.00 Red Hat Directory Server 8.0 for HP-UX provides an industry standard centralized directory service based on the Lightweight Directory Access Protocol (LDAP). You can use Red Hat Directory Server 8.0 to build an intranet or extranet directory service.
• Improved SASL Support for Kerberos Authentication Red Hat Directory Server 8.0 improves Secure Authentication and Security Layer (SASL) authentication using Generic Security Service Application Programming Interfaces (GSS-API) to a Kerberos domain. In addition, the LDAP command-line utilities (such as ldapsearch and ldapmodify) have been enhanced to support SASL. • File Hierarchy System Support Instead of installing the product in a single directory, the Red Hat Directory Server 8.
This script is similar to the setup script provided in previous Directory Server products. — /opt/dirsrv/sbin/setup-ds.pl The setup-ds.pl script creates a standalone Directory Server instance. This script is similar to the setup-ds-admin.pl script, except it does not prompt for information about the Administration Server or Configuration Directory Server. 1.3 Differences Between Red Hat Directory Server 7.1 and Red Hat Directory Server 8.
1.4 Documentation Information about Red Hat Directory Server documentation and related documentation is included in Section 6.2 (page 56). 1.5 Red Hat Directory Server 8.0 for HP-UX Directory Path Differences To conform to the standard file hierarchy system used on HP-UX, the HP-UX installation script installs the Red Hat Directory Server product in directories that differ from the directory paths shown in the Red Hat documentation set.
• • A Directory Server crash might occur after the changelog is moved to a new location on the disk (either by use of the console or by modifying the nsslapd-changelogdir attribute in the cn=changelog5,cn=config entry). Logs might expire earlier or later than the configured period when the configuration attributes are listed in a particular order in dse.ldif.
1.7 Known Problems Fixed in Red Hat Directory Server 8.0 Red Hat Directory Server 8.0 corrects the following Red Hat Directory Server 7.1 problems: • • • • • • • • • • • • • • Existing entries in subfolders were not synchronized when Windows Sync was initiated. The synchronization has been fixed so that the search scope is for the entire subtree, not just one level.
• Admin console incorrectly displays the value of the attribute as set to 1. This is incorrect, the default of these attributes is -1 (disabled). The Certificate Request Wizard returns an error when creating a certificate request The Certificate Request Wizard returns the Unable to convert DN to certificate name error when creating a certificate request. Workaround Use the certutil command-line utility to create a certificate request, or use the Certificate Request Wizard with the following workaround: 1.
• HP-UX 11i v1 Apache-based Web Server NSPR Libraries are not compatible with Red Hat Directory Server 8.0 The HP-UX 11i v1 version of the HP-UX Apache-based Web Server bundle includes a version of Netscape Portable Runtime (NSPR) that is not compatible with the Red Hat Administration Server. Workaround If you use the Red Hat Administration Server on an HP-UX 11i v1 system, move the Apache NSPR library files to an alternate location. For more information, see Section 2.1.5.1.1 (page 21).
not specify an absolute path, the console uses the default server machine path /var/opt/dirsrv/slapd-instance/ldif, which may not be valid on the remote host. You can also use the Browse button to locate an appropriate path on the remote host. NOTE: If you are importing or exporting an LDIF on the local system, you can specify the file using a relative path.
2 Installing Red Hat Directory Server 8.0 This chapter contains information that supplements the Red Hat Directory 8.0 Server Installation Guide for installing the product on HP-UX. 2.1 Preparing for Red Hat Directory Server 8.0 Installation This section describes how to prepare for installing Red Hat Directory Server 8.0. 2.1.1 Hardware Requirements Red Hat Directory Server 8.0 has the following are hardware requirements: • • HP 9000 (PA2.0) or HP Integrity system At least 256 MB of memory.
2.1.3 Operating System Requirement HP-UX 11i v1, 11i v2, or 11i v3. 2.1.4 Patches and OS Packages The following list describes patch and OS package requirements and recommendations: • HP-UX 11i v1 PHSS_38154 is required. PHSS_38154 is a ld and linker tools cumulative patch. The 64-bit components of Red Hat Directory Server 8.0 will not function correctly without this patch. HP recommends, but does not require, that you install the HP-UX Quality Pack, June 2004 or later.
HP-UX Apache-based Web Server bundles are available at the following website : http://software.hp.com/ Enter “Apache” in the search field. 2.1.5.1.1 NSPR Compatibility Problem on HP-UX 11i v1 Systems The HP-UX 11i v1 version of the HP-UX Apache-based Web Server bundle includes a version of Netscape Portable Runtime (NSPR) that is not compatible with the Red Hat Administration Server.
2.1.5.4 Requirements for Specific Features To use the following features with Red Hat Directory Server 8.0, you must install additional software on your system: • • • Kerberos authentication SNMP subagent Console online help 2.1.5.4.1 Kerberos Authentication Requirement You must install the KRB5CLIENT package to use Kerberos authentication and encryption features. The KRB5CLIENT version requirements are as follows: • • • HP-UX 11i v1: C.1.3.5.06 or later HP-UX 11i v2: D.1.6.2 or later HP-UX 11i v3: E.1.
max_thread_proc 256 (default) maxfiles 2048 (default) maxfiles_lim 4096 (default) nproc 4200 (default) To verify the current values of these kernel parameters, use the sysdef(1M) or kctune utility. For example: kctune | grep -e max_thread_proc -e maxfiles -e maxfiles_lim \ -e nproc You can expect the following output after reconfiguration: max_thread_proc 256 maxfiles 2048 maxfiles_lim 4096 nproc 4200 2.1.6.1.
2.2 Using swinstall to Install Red Hat Directory Server 8.0 Use the following steps to use swinstall to install Red Hat Directory Server 8.0: 1. 2. 3. Log in to your system as an administrator with appropriate privileges to run swinstall. Acquire the software from HP Software Depot (http://www.hp.com/go/softwaredepot) or installation media, if available. Use the swverify utility to verify the file has downloaded correctly. You must specify the full path to the depot file. For example: % # # # # 4.
NOTE: The directory paths on HP-UX systems differ from the directory paths shown in Red Hat documents. Table 1-1 (page 12) maps the Red Hat directory paths to the HP-UX directory paths. 2.3 Verifying Installation Verify the installation of the Red Hat Directory Server 8.0 using the following steps: 1.
3 Setting Up Red Hat Directory Server 8.0 This chapter describes how to set up and configure Red Hat Directory Server 8.0. 3.1 Overview If this is a new installation, use one of the following setup scripts to configure Red Hat Directory Server 8.0: • /opt/dirsrv/sbin/setup-ds-admin.pl The setup-ds-admin.pl script creates a Directory Server instance that is managed by the centralized administrative framework.
2. Start the setup-ds-admin or setup-ds.pl script. The script displays information about the setup process. Answer the following prompts. The script lists the default response in square brackets. 3. Would like to continue with set up? [yes] Enter yes or press RETURN. 4. Do you agree with the license terms? [no] Read the /opt/dirsrv/LICENSE.TXT file. If you accept the terms, enter y. 5. Choose a setup type [2]: Accept the default, option 2 (Typical Installation), to perform a typical setup.
cases, the port number is 389, the Internet Assigned Numbers Authority (IANA) registered port number for LDAP. For example: ldap://ldap.example.com:389/o=NetscapeRoot If the Configuration Directory Server uses SSL, use the following syntax: ldaps://host:port/o=NetscapeRoot In most cases, the port number is 636, the IANA registered port number for secure LDAP. For example: ldaps://ldap.example.com:636/o=NetscapeRoot b.
10. Directory server identifier [hostname]: Enter a unique identifier for this Directory Server instance. The default is the local hostname without the domain portion. NOTE: The Directory Server identifier must not contain a period. For example, server.example.com is not a valid server identifier name. 11. Suffix: Enter a distinguished name meaningful to your enterprise. The default is dc=domain_name 12.
3.3.2 Tuning Database Performance Three major parameters affect Directory Server performance: nsslapd-dbcachesize, nsslapd-cachememsize and nsslapd-cachesize. Chapter 14, "Tuning Directory Server Performance" in the Red Hat Directory Server 8.0 Administrator's Guide contains detailed information about how to configure these parameters. In addition, the Red Hat Directory Server 7.
be greater than or equal to the value of (nsslapd-cachememsize) + (nsslap-dbcachesize). CAUTION: • If you configure nsslapd-dbcachesize with nsslapd-cachememsize greater than maxdsiz or maxdsiz_64bit, the Directory Service daemon ns-slapd only expands up to the value of maxdsiz or maxdsiz_64bit. • HP does not support the following configuration: (nsslapd-dbcachesize) + (nsslapd-cachememsize) > maxdsiz_64bit (in bytes) If you use this unsupported configuration, ns-slapd might terminate. 3.3.2.
4 Supplemental Information for Administering Red Hat Directory Server 8.0 This chapter contains information that supplements the Red Hat Directory 8.0 Server Installation Guide for configuring, administering, and troubleshooting the product on HP-UX. 4.1 Stopping and Restarting the Directory Server To stop the Directory Server daemon ns-slapd, enter the following command sequence as root: cd /opt/dirsrv/slapd-instance ./stop-slapd For example: cd /opt/dirsrv/slapd-ldapA .
• • • The ldif2db.pl script for fast online import The ldif2db command-line script The ldif2ldap command-line script The ldapmodify tool is located in the /opt/dirsrv/bin directory. The ldif2db.pl, ldif2db and ldif2ldap scripts are located in the /opt/dirsrv/slapd-instance directories. 4.3.1.
4.4.1 Server Cannot Allocate Import Cache for Replica Initialization The Directory Server allocates one import cache for each online replica initialization operation. If you configure a large import cache size it is possible to configure an import cache size that is so large that the server cannot allocate the cache for replica initialization. This is most likely to occur if multiple replica initialization operations are initiated on the same server simultaneously.
supportedControl: 2.16.840.1.113730.3.4.5 supportedControl: 1.2.840.113556.1.4.473 supportedControl: 2.16.840.1.113730.3.4.9 supportedControl: 2.16.840.1.113730.3.4.16 supportedControl: 2.16.840.1.113730.3.4.15 supportedControl: 2.16.840.1.113730.3.4.17 supportedControl: 2.16.840.1.113730.3.4.14 supportedControl: 1.3.6.1.4.1.1466.29539.12 supportedControl: 2.16.840.1.113730.3.4.12 supportedControl: 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.
5 Migrating to Red Hat Directory Server 8.0 This chapter describes how to migrate a Netscape Directory Server version 6.11 or 6.21 or a Red Hat Directory Server 7.1 to Red Hat Directory Server 8.0. HP does not support migration from Netscape Directory Server 6.02 or earlier versions, such as 3.x, 4.x, 6.02, or iPlanet Directory Server 5.0. For additional information, see Chapter 8, "Migrating From Previous Versions," in the Red Hat Directory Server 8.
5.3 Migrating to Red Hat Directory Server 8.0 on the Same System This section describes how to migrate from Netscape Directory Server version 6.11, 6.21 or Red Hat Directory Server 7.1 to Red Hat Directory Server 8.0 on the same system. For information on migrating from a previous Directory Server version on an HP 9000 system to Red Hat Directory Server 8.0 an HP Integrity system, see Section 5.4 (page 43). 5.3.1 Preparing for Migration To prepare the Directory Server for migration, follow these steps: 1.
a. Enter the following command sequence to determine the database names for a Directory Server instance: cd /var/opt/netscape/servers/slapd-instance find ./db -type d Each subdirectory under the db represents a separate database, such as NetscapeRoot or userRoot. The name of the database is the same as the subdirectory name. b. For each database, enter the following command sequence to create an LDIF file in the db subdirectory below the instance directory: cd /var/opt/netscape/servers/slapd-instance .
2. Stop both the legacy Directory Server and the legacy Administrative Server (the existing servers that you are going to migrate). CAUTION: If you do not stop the legacy Directory Server instance before running the migration script, the script might erroneously apply some configuration changes to the legacy Directory Server instance instead of the new (Red Hat Directory Server 8.0) instance. NOTE: The administrator password must not be expired when you run the migration script.
NOTE: The configuration administrator is not the same as the directory manager (cn=Directory Manager). The configuration administrator (by default, the user admin) manages the server instances in the administration domain and has the DN uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot. 5.3 Migrating to Red Hat Directory Server 8.
4. Run the migration script as the root user: • To migrate from Directory Server 6.11 or 6.21 to 8.0, select one of the following options. NOTE: You must have the LDIF files created for your legacy directories. See Section 5.3.1 (page 38). — To migrate all Netscape Directory Server 6.11 or 6.21 instances and the Administration Server to Red Hat Directory Server 8.0, use the following command sequence: cd /opt/dirsrv/sbin ./migrate-ds-admin.pl --oldsroot /var/opt/netscape/servers \ --cross --file=setup.
cd /opt/dirsrv/sbin ./migrate-ds.pl --oldsroot /var/opt/netscape/server7 \ --instance slapd-instance The migration script migrates the legacy Directory Server and creates Red Hat Directory Server 8.0 Directory Servers using the configuration information from the legacy Directory Server instances. If you used the migrate-ds-admin.pl script, the script also creates a new Administration Server. The migration script also starts the new Directory Server instances and the Administration Server.
Migration from Netscape Directory Server 6.02 and earlier is not supported. For additional information about migration, see Chapter 8, "Migrating From Previous Versions" in the Red Hat Directory Server 8.0 Installation Guide before you start the migration process. IMPORTANT: A large number of configuration parameters are based on the Directory Server's host name including Console, replication, TLS/SSL. The migration scripts cannot change the host name used by the Directory Server and Administration Server.
IMPORTANT: The db_name portion of the LDIF file name must match the database name, and this name is case sensitive. For example, the LDIF file name for the NetscapeRoot database must be NetscapeRoot.ldif. Be sure to specify the -r option. This option causes the migration tool to migrate replica state information. If you do not specify the -r option, and you must re-initialize replicas after the migration completes. 4. 5.
8. On the HP-UX 11i v2 or v3 HP Integrity system, uncompress the legacy directory Server installation directory files you transferred from the legacy Directory Server. For example, the following commands uncompress the file, legacydir.tar: cd /tmp/oldserver tar -xvf legacydir.tar 5.4.2 Running the Migration Tool After transferring and extracting the files from the legacydir.tar file, complete the following steps to run the migration tool: 1. 2. Use swinstall to install Red Hat Directory Server 8.
NOTE: The configuration administrator is not the same as the directory manager (cn=Directory Manager). The configuration administrator (by default, the user admin) manages the server instances in the administration domain and has the DN uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot. 5.4 Migrating a Directory Server on an HP 9000 System to Red Hat Directory Server 8.
3. Run the appropriate migration script as the root user. For the --oldsroot argument, specify the directory that contains the uncompressed legacy Directory Server tar file contents, such as /tmp/oldserver. • To migrate from Netscape Directory Server 6.11 or 6.21, select one of the following options: — To migrate all Netscape Directory Server 6.11 or 6.21 instances and the Administration Server to Red Hat Directory Server 8.0, use the following command sequence: cd /opt/dirsrv/sbin ./migrate-ds-admin.
cd /opt/dirsrv/sbin ./migrate-ds-admin.pl --oldsroot oldserver_datadir \ --actualsroot /var/opt/netscape/server7 \ --instance slapd-instance --cross The migration script migrates the legacy Directory Server and creates Red Hat Directory Server 8.0 Directory Servers using the configuration information from the legacy Directory Server instances. If you used the migrate-ds-admin.pl script, the script also creates new a Administration Server.
CAUTION: A password file contains the password for the SSL private key token in clear text and is a security risk. If you create a password file, HP recommends that you delete it after you complete the migration. NOTE: If the server host or CA certificate is expired, the server cannot start during the migration process, and the migration fails. Although previous Directory Server versions can operate with expired certificates, Red Hat Directory Server 8.
5.5.2 Creating a Password File for the SSL Private Key Token Use the following procedure to create a password file for the SSL private key token for the legacy Directory Server. The migration script creates a copy of the file and installs it in the Red Hat Directory Server 8.0 directory /etc/opt/dirsrv/slapd-instance. 1. 2. 3. Log in as root. Stop the legacy Directory Server (the Directory Server that you are going to migrate) if you have not stopped it.
5.6 Post-Migration Tasks After you complete the migration process and verify the results, you can remove your legacy Directory Server from the system. For more information, see Section 5.6.1 (page 52) or Section 5.6.2 (page 52). If you migrated a secure Directory Server, re-enable SSL security if needed or delete the password file for the SSL private key token. For more information, see Section 5.5.1.1 (page 50) and Section 5.5.2.1 (page 51). 5.6.1 Removing Netscape Directory Server 6.11 or 6.
NOTE: 1. The commands in this procedure use the Bourne shell scripting language. Shut down the administration server: cd /opt/dirsrv/sbin ./stop-ds-admin NOTE: 2. Remove the data for the Administration Server: cd rm rm rm rm rm rm 3. The stop-ds-admin utility might report that the server is not running. /etc/opt/dirsrv/admin-serv -f admpw -f adm.conf -f cert8.db -f key3.db -f secmod.db -f local.conf Shut down the any newly created servers: cd /opt/dirsrv for name in slapd-* ; do .
6 Support and other resources 6.1 Contacting HP 6.1.1 Information to collect before contacting HP Be sure to have the following information available before you call contact HP: • • • • • • Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) 6.1.
NOTE: HP cannot provide product support through this email address. To obtain product support, contact your HP Support Representative, your HP Services Representative, or your authorized HP reseller. For more information about support services, see the support website: http://www.hp.com/go/support 6.2 Related information 6.2.1 Red Hat Directory Server documentation set Table 1-1 lists documentation available for Red Hat Directory Server 8.0.
6.3 Typographic conventions This document uses the following typographical conventions: Book title The title of a book. On the web, this can be a hyperlink to the book itself. Command A command name or command phrase, for example ls -a. Computer output Information displayed by the computer. Ctrl+x or Ctrl-x A key sequence that indicates you must hold down the keyboard key labeled Ctrl while you press the letter x. ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.
A Migration Tools This appendix provides information about the major options and arguments that the migrate-ds-admin.pl and migrate-ds.pl tools support. A.1 Major Options The migrate-ds-admin.pl and migrate-ds.pl tools support the following major options: --oldsroot -o Required. If you migrate the legacy Directory Server 6.11, 6.21 or 7.1 to Directory Server 8.0 on the same system, this option specifies the path to the installation directory of the legacy Directory Server 6.11, 6.21 or 7.
--logfile name -l name Optional. Specifies a log file to log the migration messages. If this option is not set, the migration information is written to a temporary file, /tmp/migratexxxx.log. To disable logging, set this option to /dev/null. --cross -c or -x Optional. This is used when the source system is a different architecture than the destination system. When you migrate from one system to another or migrate from one platform to another platform, you must perform cross-platform migration.
B Schema Changes Red Hat Directory Server versions 7.1 and 8.0 include changes to the LDAP schema. Red Hat Directory Server 8.0 removes multiple rarely used and application-specific schema definitions and adds new schema elements, such as those used for the new password policy features. This appendix lists schema changes introduced in Red Hat Directory Server versions 7.1 and 8.0. B.1 Red Hat Directory Server 7.1 Schema Changes This section lists differences between Red Hat Directory Server 7.
B.2.1 Object Classes Removed in Version 8.
nsmsgCfgmtaprogdeliver nsmsgCfgmtarouter nsmsgCfgmtasmtpdeliver nsmsgCfgmtaunixdeliver nsmsgCfgpartition nsmsgCfgpop nsmsgCfgpublic nsmsgCfgreport nsmsgCfgscript nsmsgCfgservice nsmsgCfgsnmp nsmsgCfgstore nsmsgCfguser nsmsgPipeProgram nswcalUser personalInterestProfile B.2.2 Attributes Removed in Version 8.
icsSubscribed icsTimezone inetResourceStatus mgmanAllowSubscribe mgmanDenySubscribe mgmanGConfAdmin mgmanGConfDefaultInheritance mgmanGConfGroupCreationUser mgmanGConfGroupDomains mgmanGConfGroupTemplate mgmanGConfKey mgmanGConfNewGroupParent mgmanGConfRemoteUserParent mgmanGConfSearchAttribute mgmanGConfSearchBase mgmanGConfSearchGroupUser mgmanGConfSearchRelationship mgmanGConfSearchTreeNode mgmanGConfSortAttributeDirMembers mgmanGConfSortAttributeGroupMembers mgmanGroupKey mgmanGroupStat mgmanHidden mgma
nsBCMimeAllowRemove nsBCMimeType nsBCNoProxiesOn nsBCOfflinePromptSynchOnExit nsBCOfflineSendUnsentMessages nsBCOfflineStartupState nsBCProxyAutoConfigUrl nsBCProxyFtp nsBCProxyGopher nsBCProxyHttp nsBCProxySocks nsBCProxySsl nsBCProxyType nsBCProxyWais nsBCRelatedAutoload nsBCRelatedDisabledForDomains nsBCRelatedEnabled nsBCStartupBrowser nsBCStartupCalendar nsBCStartupEditor nsBCStartupHomePage nsBCStartupMail nsBCStartupPage nsBCUnderlineAnchors nsBCUseDocumentColors nsBCUseDocumentFonts nsBCVisitedColor
nsCalOperatingPrefs nsCalOrgUnit2 nsCalOrgUnit3 nsCalOrgUnit4 nsCalPasswordRequired nsCalPrmd nsCalRefreshPrefs nsCalResourceCapacity nsCalResourceNumber nsCalServerVersion nsCalSysopCanWritePassword nsCalTimezone nsCalXItemId nsDADomain nsDefaultMaxDeptSize nsLIData nsLIElementType nsLIPrefs nsLIProfileName nsLIPtrURL nsLIServerType nsLIVersion nsMCAddrBookLastnameFirst nsMCAddrBookLdapDisabled nsMCAllowAtSignInUserName nsMCAllowAtSignInUserName1 nsMCAltMailDll nsMCAuthLogin nsMCAutoCompleteEnabledServerNa
nsMCNewsRemoveBodiesByAge nsMCNewsRemoveBodiesDays nsMCNewsTimeout nsMCPlaySound nsMCPop3GetsNewMail nsMCPopServer nsMCPopServerProperties nsMCPromptPurgeThreshold nsMCPurgeThreshold nsMCQuotedSize nsMCQuotedStyle nsMCReceiptRequestHeaderType nsMCRememberSelectedMessage nsMCReplyOnTop nsMCRequestReturnReceipt nsMCReuseMessageWindow nsMCSearchServer nsMCSearchSubFolders nsMCShowHeaders nsMCSkipDirectoryIfLocalMatchFound nsMCSmtpServer nsMCSmtpUseSSL nsMCSmtpUserName nsMCSpellCheckBeforeSend nsMCStrictlyMime
nsMcdUserAgent nsMcdXAnimationFile nsNumDepts nsNumDomains nsNumMailLists nsNumUsers nsPrefMap nsSearchFilter nsaclrole nscreator nsdaCapability nsdaModifiableBy nsflags nsmsgAccounturl nsmsgAdddeliveredto nsmsgAddheaders nsmsgAdmins nsmsgAlias nsmsgAllowadminproxy nsmsgAllowanonymouslogin nsmsgAllowbarelf nsmsgAllowbdat nsmsgAllowehlo nsmsgAllowetrn nsmsgAllowexpn nsmsgAllowhelp nsmsgAllowonex nsmsgAllowsize nsmsgAllowverb nsmsgAllowvrfy nsmsgAltqueues nsmsgAlwaysqueue nsmsgAuthcachesize nsmsgAuthcachettl
nsmsgDnsresolveclient nsmsgDocanonicalize nsmsgDoclientdnslookup nsmsgDodsn nsmsgDoetrn nsmsgDomainallowed nsmsgDomainlangtable nsmsgDomainname nsmsgDomainnotallowed nsmsgDomainsecurity nsmsgDorewritefromusingauth nsmsgDorewritesenderusingauth nsmsgEnable nsmsgEnablesslport nsmsgEnveloperewritemethod nsmsgExclusive nsmsgExpirestart nsmsgExpirytime nsmsgExternalmxserverip nsmsgExtrauserldapattrs nsmsgFallbacksearchmethod nsmsgFilemode nsmsgFilterurl nsmsgFlushinterval nsmsgFolderpattern nsmsgFoldersizebytes
nsmsgMaxlogfilesize nsmsgMaxlogsize nsmsgMaxmessagesize nsmsgMaxmtahops nsmsgMaxpostsize nsmsgMaxqueuetime nsmsgMaxruncount nsmsgMaxruncountdeferred nsmsgMaxscriptsize nsmsgMaxsessions nsmsgMaxstateobjectsize nsmsgMaxthreads nsmsgMessagecount nsmsgMessagedays nsmsgMessagehostname nsmsgMessagesize nsmsgMessagesizedays nsmsgMinfreediskspace nsmsgMinruncount nsmsgMsgalarmdescription nsmsgMsgalarmnoticehost nsmsgMsgalarmnoticeport nsmsgMsgalarmnoticercpt nsmsgMsgalarmnoticesender nsmsgMsgalarmnoticetemplate nsm
nsmsgReadtimeout nsmsgRenotifyinterval nsmsgRequirecrlf nsmsgReserved0 nsmsgReserved1 nsmsgReserved2 nsmsgReserved3 nsmsgReserved4 nsmsgReserved5 nsmsgReserved6 nsmsgReserved7 nsmsgReserved8 nsmsgReserved9 nsmsgResourcetimeout nsmsgRewritetocc nsmsgRolloverdelta nsmsgRolloversize nsmsgRollovertime nsmsgRoutingattribute nsmsgRoutstripimapfolders nsmsgServiceadmingroupdn nsmsgSessiontimeout nsmsgShellpath nsmsgSitelanguage nsmsgSmtphost nsmsgSmtpport nsmsgSmtprewritestyle nsmsgSourceurl nsmsgSpooldir nsmsgSsl
piphour pipidstcount pipirlist pipiroption piplastcount pipmaxhits pipmedium pipnotify pipprivilege pippwp pipreservedces1 pipreservedces2 pipreservedces3 pipreservedcis1 pipreservedcis2 pipreservedcis3 pipreservedcis4 pipreservedcis5 pipreservedcis6 pipresultset pipsortorder pipstatus pipstcategory pipstformat pipstfrequency pipsthour pipstid pipstinterest pipstirlist pipstiroption pipstlastcount pipstmaxhits pipstmedium pipstname pipstprivacy pipstquery pipstresultset pipstsortorder pipststatus pipstcateg
pipuniqueid pipusertype url B.2.3 Object Classes Added in Version 8.0 None. B.2.4 Attributes Added in Version 8.0 pamIDMapMethod passwordMaxRepeats passwordMin8bit passwordMinAlphas passwordMinCategories passwordMinDigits passwordMinLowers passwordMinSpecials passwordMinTokenLength passwordMinUppers B.2 Red Hat Directory Server 8.
C Manually Migrating a Directory Server to a System with a Different Host Name To use the automated procedure described in Section 5.4 (page 43), you must assign the source host name to the target system. If you want to migrate a Directory Server to a target system with a different host name, you can use the manual procedure described in this appendix. This procedure requires you to manually create the Administration Server on the target system.
6. 76 Use the register-ds-admin.pl script to register the migrated Directory Server instances with the Configuration Directory Server.
