Manuals / Sun Microsystems / Computer Equipment / Server

Sun Microsystems 8190994 manual Mapping the Actions Configuration, Properties

Models: 8190994

1 148

Download 148 pages 5.33 Kb

Page 104

Mapping the Actions Configuration

TABLE 6–18Mapping Between Version 5 Event Attributes and Version 6 Connection Handler

Properties	(Continued)
Directory Proxy Server 5 Attribute		Directory Proxy Server 6.0 Property

ids-proxy-con-ssl-required		is-ssl-mandatory

ids-proxy-con-bind-anonymous		allowed-auth-methods:anonymous

ids-proxy-con-bind-simple		allowed-auth-methods:simple

ids-proxy-con-bind-sasl		allowed-auth-methods:sasl

Mapping the Actions Configuration

Directory Proxy Server 5 supports only one action, specified by the ids-proxy-sch-ChangeGroupAction object class. This action enables you to configure Directory Proxy Server to change a client from one access group to another based on the evaluation of a rule. The action uses the multi-valued ids-proxy-con-to-group attribute to specify the groups to which the client can change.

Directory Proxy Server 6.0 connection handlers provide this functionality. After being classified into a connection handler, a connection can be automatically reclassified into another connection handler. For example, if a client connects anonymously, the connection is allocated to the connection handler configured for anonymous connections. If the client later provides a bind DN on the same connection, the connection can be reallocated to another connection handler.

For information on how to configure this functionality in Directory Proxy Server 6.0, see “Creating, Configuring, and Deleting Connection Handlers” in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.

Configuring Directory Proxy Server 6.0 as a Simple Connection-Based Router

It is possible to configure an instance of Directory Proxy Server 6.0 to behave as a simple connection-based router, with the same functionality as Directory Proxy Server 5.2. To do this, map the configuration attributes described previously and follow the procedure describe in “Configuring Directory Proxy Server as a Connection Based Router” in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide

104	Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007

Sun Confidential: Registered

Image 104

Sun Microsystems 8190994 manual Mapping the Actions Configuration, Properties

Contents

Enterprise Edition 6.0 Migration Guide Sun Java System Directory ServerSun Microsystems, Inc 4150 Network Circle Santa Clara, CA U.S.A Sun Confidential RegisteredSun Confidential Registered This distribution may include materials developed by third partiesContents 2 Automated Migration Using the dsmig Command1 Overview of the Migration Process for Directory Server 3 Migrating Directory Server ManuallyMigrating the Schema Manually New Plug-Ins in Directory Server 7 Migrating Identity Synchronization for Windows Sun Confidential Registered IndexContents Sun Confidential Registered Figures Migrating a Single-Host DeploymentMigrating a Multi-Master Replication Deployment Migrating a Multi-Host Deployment with Windows NTSun Confidential Registered Tables Mapping Between 5 and 6.0 Password Policy AttributesTools Previously Under ServerRoot/shared/bin Location of Certificate and Key FilesTables Sample Export Configuration File ExamplesSun Confidential Registered EXAMPLESun Confidential Registered Preface Who Should Use This BookBefore You Read This Book How This Book Is OrganizedDirectory Server Enterprise Edition Documentation Set TABLE P-1 Directory Server Enterprise Edition DocumentationRelated Reading TABLE P-1 Directory Server Enterprise Edition DocumentationContinued http//docs.sun.com/coll/DirEdit05q1Redistributable Files Default Paths and Command LocationsDefault Paths TABLE P-2 Default Paths Java Enterprise System installer, the default install-path isSun Confidential Registered of Directory Server or Directory ProxyCommand Locations TABLE P-3 Command LocationsTypographic Conventions TABLE P-3 Command LocationsContinued TABLE P-4 Typographic ConventionsShell Prompts in Command Examples Symbol ConventionsSymbol Conventions ContinuedSearching Sun Product Documentation Documentation, Support, and TrainingThird-Party Web Site References Sun Welcomes Your Comments Overview of the Migration Process for Directory Server Before You Migrate“Before You Migrate” on page “Deciding on the New Product Distribution” on pageBefore You Migrate Prerequisites to Migrating a Single Directory Server Instance FromPrerequisites to Migrating a Single Directory Server Instance From Deciding on the New Product Distribution Outline of Migration StepsDeciding on Automatic or Manual Migration TABLE 1-1 Migration Matrix Showing Support for Automated MigrationAutomated Migration Using the dsmig Command “Using dsmig to Migrate the Schema” on page“Using dsmig to Migrate Security Data” on page “Using dsmig to Migrate Configuration Data” on pageUsing dsmig to Migrate the Schema Prerequisites for Running dsmigUsing dsmig to Migrate Security Data Using dsmig to Migrate Configuration Data$ dsmig migrate-config old-instance-path new-instance-path $ dsmig migrate-security old-instance-path new-instance-pathPlug-in Configuration Data Chained Suffix Configuration DataConfiguration Data For Suffixes With Multiple Backends Replication Configuration DataConfiguration Data for o=netscapeRoot Configuration Attributes Not Migrated by dsmignsabandonedsearchcheckinterval $ dsmig migrate-data old-instance-path new-instance-path Using dsmig to Migrate User DataTasks to be Performed After Automatic Migration Sun Confidential Registered “Migrating the Schema Manually” on page “Migrating Configuration Data Manually” on page“Migrating Security Settings Manually” on page Migrating Directory Server ManuallyMigration of Specific Configuration Attributes Migrating the Schema ManuallyMigrating Configuration Data Manually Chapter 3 Migrating Directory Server Manually Global Configuration AttributesMigrating Configuration Data Manually Mapping Tree Configuration Attributes Security Configuration AttributesFeature Configuration Attributes Replication Configuration Attributes Fractional Replication Configuration AttributesReplica Configuration Attributes Change Log AttributesPassword Policy Configuration Attributes Replication Agreement ConfigurationTABLE 3-3 Mapping Between 5 and 6.0 Password Policy Attributes UniqueID Generator Configuration Attributes Database Configuration AttributesSNMP Attributes TABLE 3-3 Mapping Between 5 and 6.0 Password Policy AttributesChained Suffix Attributes Plug-In Configuration Attributes Class of Service Plug-In7-Bit Check Plug-In DSML Frontend Plug-InPass Through Authentication Plug-In Password Synchronization Plug-InReferential Integrity Plug-In Retro Change Log Plug-InMigrating Security Settings Manually Migrating User Data Manually Migrating User Plug-Ins Manually Migrating User Plug-Ins ManuallyTasks to be Performed After Manual Migration “Issues Related to Migrating Replicated Servers” on page Migrating a Replicated TopologyOverview of Migrating Replicated Servers “Overview of Migrating Replicated Servers” on pageIssues Related to Migrating Replicated Servers Issues With the New Password PolicyMigration of Replication Agreements Migration of ReferralsNew Replication Recommendations Manual Reset of Replication CredentialsProblems Related to Tombstone Purging Migrating the Consumers Migration ScenariosMigrating a Replicated Topology to an Identical Topology FIGURE 4-1 Existing version 5 Topology FIGURE 4-2 Isolating the Consumer From the TopologyMigration Scenarios Chapter 4 Migrating a Replicated TopologyThe next step involves migrating the version 5 consumer Migrating the Hubs FIGURE 4-5 Existing version 5 Topology With Migrated Consumers FIGURE 4-6 Isolating the Hub From the TopologyMigration Scenarios 6.0 Consumer BThe next step involves migrating the version 5 hub FIGURE 4-7 Migrating the version 5 HubMigration Scenarios Chapter 4 Migrating a Replicated TopologyMigrating the Masters 9. If you have migrated the data, check that replication is in sync The next step involves migrating the version 5 master FIGURE 4-10 Isolating the Master From the TopologyFIGURE 4-11 Migrating the version 5 Master Migration ScenariosMigrating a Replicated Topology to a New Topology Migrating All the Servers FIGURE 4-13 Existing version 5 TopologyPromoting the Hubs FIGURE 4-14 Existing Topology With Migrated ServersPromoting the Consumers FIGURE 4-15 Migrated Topology With Promoted Hub ReplicasMigrating Over Multiple Data Centers Sun Confidential Registered Changes in the Administration Framework “Changes in the Administration Framework” on page“Changes to ACIs” on page “Command Line Changes” on page “Changes to the Console” on page “New Password Policy” on pageChanges to ACIs Removal of the o=netscapeRoot SuffixChanges in the ACI Scope Changes in Suffix-Level ACIsCommand Line Changes TABLE 5-1 Directory Server 5 and 6 commands Version 6.0 CommandContinued Sun Confidential RegisteredDeprecated Commands TABLE 5-1 Directory Server 5 and 6 commandsTABLE 5-3 Version 5 Commands That Have Been Deprecated ContinuedNew Password Policy Changes to the ConsolePassword Policy Compatibility The pwd-compat-mode property can have one of the following values Changes to Plug-Ins New Plug-Ins in Directory ServerChanges to the Plug-In API Changes to the Installed Product LayoutPlug-Ins Deprecated in Directory Server Administration Utilities Previously Under ServerRoot Binaries Previously Under ServerRoot/binOnline Help Previously Under ServerRoot/manual Libraries and Plug-Ins Previously Under ServerRoot/libPlug-Ins Previously Under ServerRoot/plugins Utilities Previously Under ServerRoot/shared/binCertificate and Key Files TABLE 5-5 Tools Previously Under ServerRoot/shared/binContinued TABLE 5-6 Location of Certificate and Key FilesSilent Installation and Uninstallation Templates Server Instance Scripts Previously UnderServer Instance Subdirectories ServerRoot/slapd-ServerIDMapping the Global Configuration “Mapping the Global Configuration” on page“Mapping the Connection Pool Configuration” on page “Mapping the Groups Configuration” on pageMapping the Global Configuration Mapping the Global Security Configuration TABLE 6-2 Mapping of Security Configuration Access Control on the Proxy ConfigurationManaging Certificates Mapping the Connection Pool Configuration TABLE 6-3 Mapping of Connection Pool AttributesMapping the Groups Configuration Mapping the Group ObjectCONNECTION-HANDLER-NAME is-ssl-mandatoryfalse Mapping the Network Group ObjectCONNECTION-HANDLER-NAME is-ssl-mandatorytrue Mapping Bind Forwarding Set this as a property for a specific listener port by usingThis functionality exists but with less granularity than in Directory Proxy Server 5. Set this limit as a property for a$ dpconf help-properties grep request-filtering-policy Mapping Operation ForwardingConnection Handler Property Settings $ dpconf help-properties grep resource-limits-policy Mapping Subtree HidingMapping Search Request Controls Mapping Compare Request Controls Mapping Attributes Modifying Search RequestsMapping Attributes Restricting Search Responses $ dpconf help-properties grep search-data-hiding-ruleDirectory Proxy Server 6.0 Properties Mapping the Referral Configuration AttributesDirectory Proxy Server 5 Attributes Mapping the Server Load Configuration Forbidden Entry Property Mapping the Properties ConfigurationAttribute Renaming Property LDAP Server Property $ dpconf help-properties grep ldap-data-sourceLoad Balancing Property Enterprise Edition 6.0 Administration GuideSource” in Sun Java System Directory Server Sun Confidential RegisteredEnterprise Edition 6.0 Administration Guide Monitoring Backend ServersSearch Size Limit Property Log Property$ dpconf set-access-log-prop PROPERTYVALUE TABLE 6-17 Version 5 and Version 6 Log FunctionalityMapping the Events Configuration Mapping the Events ConfigurationMapping the Actions Configuration Properties“What to Do if the 1.1 Uninstallation Fails” on page Migrating Identity Synchronization for Windows“Migration Overview” on page “Before You Migrate Identity Synchronization for Windows” on pageMigration Overview Before You Migrate Identity Synchronization for WindowsExporting Version 1.1 Configuration Preparing for Identity Synchronization for Windows MigrationUsing the export11cnf Utility Inserting Clear-Text PasswordsSample Export Configuration File cleartextPassword=Continued index=0 location=ou=people,dc=example,dc=com filter=Continued TopologyHost TopologyHostEXAMPLE 7-1 Sample Export Configuration File ContinuedAttributeMap AttributeDescription parent.attr=SunAttribute name=uniquemember syntax=1.3.6.1.4.1.1466.115.121.1.25INSERT PASSWORD BETWEEN THE DOUBLE QUOTES IN THE ABOVE ContinuedUsing the checktopics Utility Checking for Undelivered MessagesTo Clear Messages 2 From a command prompt, type the subcommand as follows2 Wait until the messages are applied to the destination connector 1 Open a Terminal window and cd to the migration directoryForcing Password Changes on Windows NT Migrating Your SystemPreparing for Migration Use the following procedure to prepare for migration to version3 Add passwords to the exported XML file Preparing to migrate from version 1.1, and 1.1 SP1, to version2 Export your version 1.1 configuration settings to an XML file b. Save the NT Change Detector Service counters 5 Verify that your system is in a stable state7 On Windows NT only, perform the following steps i. Open the Registry Editor by executing regedt32.exeUninstalling Identity Synchronization for Windows To Uninstall Identity Synchronization for Windows VersionOn Solaris Type serverRoot \/slapd-hostname \/restart-slapd On Windows Type serverRoot\\\slapd- hostname\\\restart-slapd.batOn Solaris or SPARC Type ./runUninstaller.sh On Windows Type \\runUninstaller.batTo install the Identity Synchronization for Windows 6.0 components Installing or Upgrading the Dependent ProductsInstalling Identity Synchronization for Windows cd serverRoot\isw-hostname\bin idsync prepds arguments\9 Start the service and the synchronization What to Do if the 1.1 Uninstallation Fails Manually Uninstalling 1.1 Core and Instances from Solaris“Manually Uninstalling 1.1 Core and Instances from Solaris” on page “Manually Uninstalling a 1.1 Instance from Windows NT” on pageTo Manually Uninstall Core From a Solaris Machine etc/init.d/imq stop4 Remove the Directory Server Plugin 5 Back-up copy and rename the current productregistry file located in f. Stop Directory Serverh. Restart Directory Server 8 Clean up the configuration directory as follows Manually Uninstalling 1.1 Core and Instances from Windows 10 Clean up all other Console-related files as followsa. Remove all the Console jar files by typing b. Remove all the Console servlet jar files by typingTo uninstall Core from a Windows 2000 machine serverRoot\isw-hostname\Core and Instances from Windows 2000” on page net stop slapd-myhostnameb. Select Registry →Export Registry File from the menu bar 4 In the Registry Editor, select Edit →Delete from the menu bar8 Clean up the configuration directory as follows Manually Uninstalling a 1.1 Instance from Windows NT serverRoot\\\isw-hostname\ a. Open the Services window, right-click on Change Detector Service and select Properties a. Select the registry key entry in the left pane 10 Restart your machine for all changes to take effect Other Migration Scenarios9 Remove the Password Filter DLL “Multi-Host Deployment with Windows NT” on page Multi-Master Replication Deployment“Multi-Master Replication Deployment” on page Multi-Host Deployment with Windows NT Three hosts are used in this deployment scenario A Windows NT systemA host for all other components Password Changes on Both Directory Server Masters are Lost FIGURE 7-3 Migrating a Multi-Host Deployment with Windows NTChecking the Logs Index instance-path Page XML configuration documents Continued