VDS3.5 Getting Started Guide

Reviews

Tags

VDS3.5 Getting Started Guide, Getting Started, service level, beneficial business relationship, client manager, document publishing, service agreement, fact sheets, mutually beneficial, Fixed Price Agreement

Stats

views:: 6
rating:: not rated
reviews:: 0
posted:: 6/15/2009
language:: English
pages:: 0

Public Domain

VDS 3.5 Getting Started Guide Todd Schwind (todd@symlabs.com) August 15, 2007 1 Overview The purpose of this document is to provide a simple set of instructions that allows a user to quickly and easily download, install and conﬁgure Symlabs’ Virtual Directory Server (VDS). The information contained in this guide will provide a user with a basic understanding of how to get the VDS up and running as well as provide an introduction into conﬁguring the product in a lab environment. This guide does not address some of the more advanced functionality that VDS provides and should not be used as a reference manual for a production deployment. For this type of information please consult the VDS Administration and Developer Guides. This guide contains integration documentation for a couple of common systems (i.e. database, directory and other), however, it is by no means an exhaustive list. For more information please consult the VDS Identity Store Conﬁguration Guide. 1.1 Input (Listeners) Listeners are the "input" for VDS. It is the network port where applications will connect to. In order for VDS to work properly, at least one listener must be conﬁgured. Listeners are conﬁgured by specifying the protocol which they should support, a network port and an optional listen ip address. You can create multiple listeners on different ports and/or IP addresses. If you do not specify a list IP address, VDS will by default listen on the speciﬁed port on all IP addresses that the system has. Otherwise, the listener will only listen on the speciﬁed port of the speciﬁed IP address. 1.2 Processing (Stages) Stages contain processing rules that intercept requests and responses, and act on them. There are many different plugins bundled with VDS that implement a variety of useful functionality out-of-the-box. It is also possible to write customized processing rules using our DirectoryScript language and inserting them into a stage. 1 1.3 Output (Server Groups) 2 VDS INSTALLATION Two types of stages exist: automatic and manual. Automatic stages allow you to harness the bundled plugins (also known as standard scriptlets) that come with VDS. These plugins are easily conﬁgured using the GUI. Manual stages can be used by experienced users to write their own rules in scriptlets. 1.3 Output (Server Groups) Server groups are the output of VDS. They are the back-end servers that VDS will send requests to. In typical conﬁgurations, you will need to deﬁne at least one server group. Server groups are typically back-end LDAP servers or relational databases, although it is also possible to create server groups that use different protocols or access mechanisms in more advanced conﬁgurations. There are two types of server groups, automatic and manual. Automatic server groups are by far the most commonly used type. Manual server groups are not covered in this guide, however, more information can be found in the VDS Administrator Guide. If your back-end server does not allow anonymous binds then you will need to conﬁgure connection pooling. Each of the tutorials in this document utilize connection pooling for this purpose, however, there are other reasons why you may want to utilize connection pooling. For more information regarding this topic, refer to the VDS Administrator Guide. 2 2.1 VDS Installation Supported Operating Systems The following operating systems are supported for installation of Symlabs VDS: • Windows • Solaris • Linux • HP / UX • AIX In this guide, we cover installation and conﬁguration relating to Windows, Solaris and Linux only. If you’re going to be installing VDS on another platform, please contact Symlabs for further technical support. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 2 2.2 Windows 2 VDS INSTALLATION 2.2 2.2.1 Windows Installation and OS Conﬁguration 1. Execute the .exe ﬁle then follow along with the InstallAnywhere wizard. 2. To run VDS as a windows service, see Appendix A. 2.2.2 Launch Application 1. Click Start. 2. Click All Programs. 3. Click Symlabs. 4. Click DE. 5. Click Rx.x.x. 6. Click Symlabs Directory Extender Rx.x.x. and you’ll see the following: Figure 1: VDS Windows installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 3 2.3 Linux 2 VDS INSTALLATION 2.3 2.3.1 Linux Installation and OS Conﬁguration VDS is provided as an rpm package. This package should be copied into the /opt directory and can then be added to the system as any other package would be using the rpm utility: mkdir /opt (if necessary) cd /opt rpm -ihv ./SYMde-ev-R3.1.lin.i386.rpm After a successful installation, the rpm ﬁle can be deleted to free disk space. Set PATH variable to be able to execute VDS commands easily for the current session: PATH=\$PATH:/opt/ds/std/bin To keep this directory in your path even after reboot, you need to modify the appropriate ﬁle on your system (most likely /etc/proﬁle). 2.3.2 Launch Application Start the VDS Administration Console by typing the following from the command line: dsgui If you get the following error: dsgui: Command not found then make sure that the directory /opt/ds/std/bin is contained in your PATH environment variable. Otherwise you will see the following: 2.4 2.4.1 Solaris Installation and OS Conﬁguration Installation on Sun Solaris systems is done by running the pkgadd system utility on the ﬁle SYMdsprx.pkg. In order to install the product the package ﬁle must be copied to a temporary directory on your machine (i.e. /var/tmp). Then the pkgadd utility must be invoked using the command-line: pkgadd -d /var/tmp/SYMdsprx August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 4 2.4 Solaris 2 VDS INSTALLATION Figure 2: VDS Linux installation Once the package has been successfully installed, you can check the timestamp of the installation and the version of the installed product using the following command: pkgadd -v SYMdsprx Upon completion of a successful installation, the SYMdsprx.pkg ﬁle can be deleted from the temporary directory. Set path environment variable to be able to execute VDS commands easily: PATH=\$PATH:/opt/ds/std/bin 2.4.2 Launch Application Start the VDS Administration Console by typing the following from the command line: dsgui If you get the following error: dsgui: Command not found then make sure that the directory /opt/ds/std/bin is contained in your PATH environment variable. Otherwise you will see the following: August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 5 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 3: VDS Solaris installation 3 3.1 Tutorial #1 - Merge Users From Multiple Directories Overview There can be many reasons why an organization would need to take users from many systems and present them as one. In many large enterprises, some users exist in one database or directory while another group of users exists in a different system. As an example, a lot of HR systems contain employee records only. This excludes contractors and temporary employees. There are applications (ex. address book) that require all of that user information but can read from only one source. The VDS solves this problem by presenting users from multiple systems as a single system. In this tutorial, the users from multiple directories are going to appear to exist in a single directory branch. 3.2 Assumptions 1. VDS is installed and conﬁgured properly; VDS is currently running. 2. Directory 1 & 2 are both installed and accessible from the computer on which VDS is installed. 3. Both of your directories are populated with users. 4. None of the users in Directory 1 exist in Directory 2 and vice versa. 5. Directory 1 & 2 are both accessible on port 389 (default ldap port) August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 6 3.3 Create a TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES 3 New Conﬁguration 6. You have a good understanding of the DIT structure of your directories. 7. Port 3890 is available on the computer in which VDS is installed. 3.3 Create a New Conﬁguration 1. Click File on the menu bar, then click New. 2. Click the OK button when asked which server you want to create the new conﬁguration in (the default server is Local. 3. Enter MergeTutorial for the ﬁlename when prompted, then click the Save button and the following will appear: Figure 4: Merge Users saved conﬁguration 3.4 Server Group Conﬁguration Server Groups are the directories and / or databases where your user information is stored. Examples include Active Directory, Sun Directory Server and Oracle database. For this tutorial we will be creating two Server Groups, one for Directory 1 and another for Directory 2. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 7 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES 3.4.1 Add Directory 1 1. Click on the Output button on the left-hand side of the application and the following will appear: Figure 5: Adding a new server group 2. Click on the New Server Group button near the bottom of the screen. 3. Enter Directory 1 for your new Server Group and leave the Server Group Type as Automatic and then click the Okay button. 4. Click on the Directory 1 button on the left-hand side of the screen and the following will appear: 5. Verify that the Protocol is set to ldap. 6. Under the Servers tab, enter the Hostname / IP Address and the Port of Directory 1. 7. Click on the Connection Pooling tab and check the Use Connection Pooling checkbox. The following will appear: 8. Click on the Use Fixed Credentials radio button then enter the Bind DN and Password for the user that has appropriate access to Directory 1. 9. Change the number of Pool Connections from 10 to 2. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 8 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 6: Conﬁguring the server group August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 9 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 7: Conﬁguring connection pooling 10. Click the OK button near the top of the application to save the Directory 1 Server Group Conﬁguration. 3.4.2 Add Directory 2 1. Click on the Output button on the left-hand side of the application and the following will appear: 2. Click on the New Server Group button near the bottom of the screen. 3. Enter Directory 2 for your new Server Group and leave the Server Group Type as Automatic and then click the Okay button. 4. Click on the Directory 2 button on the left-hand side of the screen and the following will appear: 5. Verify that the Protocol is set to ldap. 6. Under the Servers tab, enter the Hostname / IP Address and the Port of Directory 2. 7. Click on the Connection Pooling tab and check the Use Connection Pooling checkbox. The following will appear: August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 10 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 8: Adding another server group August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 11 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 9: Conﬁguring the second server group August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 12 3.4 Server Group Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Figure 10: Conﬁguring connection pooling on server group 2 August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 13 3.5 Processing Conﬁguration MERGE USERS FROM MULTIPLE DIRECTORIES 3 TUTORIAL #1 - 8. Click on the Use Fixed Credentials radio button then enter the Bind DN and Password for the user that has appropriate access to Directory 2. 9. Change the number of Pool Connections from 10 to 2. 10. Click the OK button near the top of the application to save the Directory 2, Server Group Conﬁguration. 3.5 Processing Conﬁguration This is where we are going to conﬁgure the VDS to provide the functionality that we want. VDS uses the term Stage to describe this functionality. You can have multiple stages to implement different functionality in a single deployment of VDS. In this tutorial we will be implementing a single Stage. This stage is going to utilize a default plugin that will merge users from two directories into one virtual directory. This plugin is called the Merge Trees default plugin and is provided by the VDS to allow you to quickly and easily implement the functionality that you’re looking for. 1. Click on the Processing button on the left-hand side of the application and the following will appear: Figure 11: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 14 3.5 Processing Conﬁguration MERGE USERS FROM MULTIPLE DIRECTORIES 3 TUTORIAL #1 - 2. Click on the New Stage button near the bottom of the screen. 3. Enter Merge Users as the name of the new stage and leave the stage type as Automatic and then click the Okay button. 4. Click on the stage=Merge Users button on the left-hand side of the screen. 5. Click on the Add Plugin button and the following will appear: Figure 12: VDS Solaris installation 6. Scroll to the bottom of the list, click on Merge Trees and click the OK button. 7. Click the Merge Trees button on the left-hand side of the screen and the following will appear: 8. Under the Merge Tree Conﬁguration section, double-click the blank box under Server Group and select Directory 1 from the drop-down menu. 9. Under the Merge Tree Conﬁguration section, double-click the blank box under DN of Tree to merge and enter the DN(s) of the tree(s) in Directory 1 that you’d like to have merged into the VDS (ex. cn=Users,dc=company,dc=com). 10. Repeat steps 8 & 9 for Directory 2. 11. Under the Merge Tree Conﬁguration section, enter the DN for your new VDS in the Joined Tree DN text box. This will be the DN that contains all of your users from both Directory 1 and 2 that you have decided to merge in steps 8-10 above. This will also be the Base DN you specify when conﬁguring a LDAP browser or application to connect to the VDS. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 15 3.5 Processing Conﬁguration MERGE USERS FROM MULTIPLE DIRECTORIES 3 TUTORIAL #1 - Figure 13: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 16 3.6 Listener TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES 3 Conﬁguration 12. Under the Condition section, enter the DN for your new VDS in the BaseDN text box. Note that this DN should be identical to the Joined Tree DN speciﬁed in the step above. 13. Click the OK button near the top of the application to save the Processing Conﬁguration. 3.6 Listener Conﬁguration 1. Click on the Input button on the left-hand side of the application and the following will appear: Figure 14: VDS Solaris installation 2. Click on the New Listener button near the bottom of the screen. 3. Enter Merge Users for the new input / listener and then click the Okay button. 4. Click on the listener=Merge Users button on the left-hand side of the screen and the following will appear: 5. Under the Main Listener Properties tab, make sure the Protocol is set to ldap. 6. Under the Main Listener Properties tab, set the port to 3890. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 17 3.6 Listener TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES 3 Conﬁguration Figure 15: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 18 3.7 Save 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES Conﬁguration 7. Under the Main Listener Properties tab, select Directory 1 from the dropdown box to the right of Default Server Group. 8. Click on the Attached Stages tab and the following will appear: Figure 16: VDS Solaris installation 9. Double-click where it shows to do so and click on stage=Merge Users in the dropdown box. 10. Click the OK button near the top of the screen to save the Listener conﬁguration. 3.7 Save Conﬁguration When you created the new conﬁguration you were prompted to enter a ﬁlename for your conﬁguration. The ﬁle type for this ﬁle is ldif. The conﬁguration must be saved before the VDS can be launched for the ﬁrst time. Also, the conﬁguration must be saved and the VDS re-launched before changes to the conﬁguration will take effect. 1. Click on the File button on the menu bar. 2. Click Save and your conﬁguration will then be ready to launch. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 19 3.8 Launch and Test Conﬁguration 3 TUTORIAL #1 - MERGE USERS FROM MULTIPLE DIRECTORIES 3.8 Launch and Test Conﬁguration 1. Click the Process button on the menu bar. 2. Click Run on the drop-down menu. At this point the VDS is running and is ready to accept LDAP requests. 3. Click the Extras button on the menu bar. 4. Click LDAP Browser on the drop-down menu and the following will appear: Figure 17: VDS Solaris installation 5. In the Name textbox, enter Merge Users. 6. In the Hostname textbox, enter the IP Address of the computer that VDS is installed on. 7. In the Port textbox, enter 3890. 8. In the Root Sufﬁx textbox, enter the Joined Tree DN you speciﬁed during the Processing Conﬁguration section of this tutorial. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 20 4 TUTORIAL #2 - FRAGMENTED IDENTITIES 9. In the Bind DN textbox, enter the DN of the user that has appropriate access Root Sufﬁx / Joined Tree DN in the step above. 10. Enter the Password twice for the user speciﬁed in the step above. 11. Click the Test button to verify that you can properly bind to the Joined Tree DN. 12. Assuming you entered the correct information, a Test Successful! message will appear. Click the OK button. 13. Click the OK button on the next page and you will be asked if you would like to save Merge Users. Click the Yes button and the Joined Tree DN you speciﬁed will appear. 14. You can now browse the newly created branch and verify that users from both Directory 1 and 2 are included in the branch. 4 4.1 Tutorial #2 - Fragmented Identities Overview Many organizations have multiple Identity Stores (ex. LDAP directories, relational databases and other repositories), each of which contain fragments of identity data. This distribution of data is problematic for applications that need to access identity information for authorization, veriﬁcation or other reasons. VDS can solve this issue by providing a uniﬁed view of the fragmented identities, effectively collecting all the pieces from the different Identity Stores and presenting them as a single identity to multiple applications. This is done using the "Join" module that comes with VDS (see the Processing Conﬁguration section below). 4.2 Assumptions 1. VDS is installed and conﬁgured properly; VDS is currently running. 2. Directory 1 and 2 are installed and accessible from the computer on which VDS is installed. 3. Multiple users exist in both directories and share a common attribute value. 4. Both directories are accessible on port 389 (default ldap port) 5. You have a good understanding of the DIT structure of your directories. 6. Port 3890 is available on the computer in which VDS is installed. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 21 4.3 Create a New Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES 4.3 Create a New Conﬁguration 1. Click File on the menu bar, then click New. 2. Click the OK button when asked which server you want to create the new conﬁguration in (the default server is Local. 3. Enter JoinTutorial for the ﬁlename when prompted, then click the Save button and the following will appear: Figure 18: VDS Solaris installation 4.4 Server Group Conﬁguration Server Groups are the directories and / or databases where your user information is stored. Examples include Active Directory, Sun Directory Server and Oracle database. For this tutorial we will be creating two Server Groups, one for Directory 1 and another for Directory 2. 4.4.1 Add Directory 1 1. Click on the Output button on the left-hand side of the application and the following will appear: August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 22 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 19: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 23 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES 2. Click on the New Server Group button near the bottom of the screen. 3. Enter Directory 1 for your new Server Group and leave the Server Group Type as Automatic and then click the Okay button. 4. Click on the Directory 1 button on the left-hand side of the screen and the following will appear: Figure 20: VDS Solaris installation 5. Verify that the Protocol is set to ldap. 6. Under the Servers tab, enter the Hostname / IP Address and the Port of Directory 1. 7. Click on the Connection Pooling tab and check the Use Connection Pooling checkbox. The following will appear: 8. Click on the Use Fixed Credentials radio button then enter the Bind DN and Password for the user that has appropriate access to Directory 1. 9. Change the number of Pool Connections from 10 to 2. 10. Click the OK button near the top of the application to save the Directory 1 Server Group Conﬁguration. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 24 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 21: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 25 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES 4.4.2 Add Directory 2 1. Click on the Output button on the left-hand side of the application and the following will appear: Figure 22: VDS Solaris installation 2. Click on the New Server Group button near the bottom of the screen. 3. Enter Directory 2 for your new Server Group and leave the Server Group Type as Automatic and then click the Okay button. 4. Click on the Directory 2 button on the left-hand side of the screen and the following will appear: 5. Verify that the Protocol is set to ldap. 6. Under the Servers tab, enter the Hostname / IP Address and the Port of Directory 2. 7. Click on the Connection Pooling tab and check the Use Connection Pooling checkbox. The following will appear: 8. Click on the Use Fixed Credentials radio button then enter the Bind DN and Password for the user that has appropriate access to Directory 2. 9. Change the number of Pool Connections from 10 to 2. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 26 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 23: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 27 4.4 Server Group Conﬁguration4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 24: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 28 4.5 Processing Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES 10. Click the OK button near the top of the application to save the Directory 2, Server Group Conﬁguration. 4.5 Processing Conﬁguration In this tutorial we will be implementing a single Stage. This stage is going to utilize a default plugin that will merge users from two directories into one virtual directory. This plugin is called the Join Trees default plugin and is provided by the VDS to allow you to quickly and easily implement the functionality that you’re looking for. The Join module uses one attribute as the "join key" in order to match entries across different Identity Stores. This join key is an attribute that is used as the common link between several identities from multiple Identity Stores. The join key attribute values must be unique in every repository to ensure that the joins occur successfully. 1. Click on the Processing button on the left-hand side of the application and the following will appear: Figure 25: VDS Solaris installation 2. Click on the New Stage button near the bottom of the screen. 3. Enter Join Users as the name of the new stage and leave the stage type as Automatic and then click the Okay button. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 29 4.5 Processing Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES 4. Click on the stage=Join Users button on the left-hand side of the screen. 5. Click on the Add Plugin button and the following will appear: Figure 26: VDS Solaris installation 6. Scroll to the bottom of the list, click on Join Entries and click the OK button. 7. Click the JoinEntries button on the left-hand side of the screen and the following will appear: 8. Under the Condition section, enter the DN for your new VDS in the Base DN text box. This will be the DN that contains all of the attributes for your users that exist in Directory 1 and 2. This will also be the Base DN you specify when conﬁguring a LDAP browser or application to connect to the VDS. 9. Under the Join Entries Main Conﬁguration section, enter an attribute in the Primary Join Attribute textbox. 10. Under the Join Entries Main Conﬁguration section, uncheck the checkbox if the attribute is not part of the RDN otherwise leave it checked (default). 11. Click the OK button near the top of the screen to save the Main Entry conﬁguration. 12. Click on the New Foreign Data Group button and enter Directory 2 for the name of the new foreign data group then click the OK button. 13. Click on Directory 2 on the left-hand side of the screen and the following will appear: August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 30 4.5 Processing Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 27: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 31 4.5 Processing Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 28: VDS Solaris installation August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 32 4.6 Listener Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES 14. Enter the appropriate attribute in the Primary Key Attribute: section. 15. Uncheck the checkbox if the Primary Key Attribute is not part of the RDN otherwise leave it checked (default). 16. Click on Directory 2 in the dropdown box when asked which Server Group the information should be fetched from. 17. Enter the Base DN where information should be fetched from. 18. Click the OK button near the top of the screen to save the Foreign Data Group conﬁguration. 4.6 Listener Conﬁguration 1. Click on the Input button on the left-hand side of the application and the following will appear: Figure 29: VDS Solaris installation 2. Click on the New Listener button near the bottom of the screen. 3. Enter Join Users for the new input / listener and then click the Okay button. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 33 4.7 Save Conﬁguration 4 TUTORIAL #2 - FRAGMENTED IDENTITIES Figure 30: VDS Solaris installation 4. Click on the listener=Join Users button on the left-hand side of the screen and the following will appear: 5. Under the Main Listener Properties tab, make sure the Protocol is set to ldap. 6. Under the Main Listener Properties tab, set the port to 3890. 7. Under the Main Listener Properties tab, set the Default Server Group to Directory 1 by selecting it from the dropdown box. 8. Click on the Attached Stages tab. 9. Double-click where it shows to do so and click on stage=Join Users in the dropdown box. 10. Click the OK button near the top of the screen to save the Listener conﬁguration. 4.7 Save Conﬁguration When you created the new conﬁguration you were prompted to enter a ﬁlename for your conﬁguration. The ﬁle type for this ﬁle is ldif. The conﬁguration must be saved before the VDS can be launched for the ﬁrst time. Also, the conﬁguration must be saved and the VDS re-launched before changes to the conﬁguration will take effect. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 34 4.8 Launch and Test Conﬁguration TUTORIAL #2 - FRAGMENTED IDENTITIES 4 1. Click on the File button on the menu bar. 2. Click Save and your conﬁguration will then be ready to launch. 4.8 Launch and Test Conﬁguration 1. Click the Process button on the menu bar. 2. Click Run on the drop-down menu. At this point the VDS is running and is ready to accept LDAP requests. 3. Click the Extras button on the menu bar. 4. Click LDAP Browser on the drop-down menu and the following will appear: Figure 31: VDS Solaris installation 5. In the Name textbox, enter Join Users. 6. In the Hostname textbox, enter the IP Address of the computer that VDS is installed on. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 35 5 APPENDIX A - RUN VDS AS A WINDOWS SERVICE 7. In the Port textbox, enter 3890. 8. In the Root Sufﬁx textbox, enter the Base DN from the Condition section of the Main Entry Conﬁguration you speciﬁed during the Processing Conﬁguration section of this tutorial. 9. In the Bind DN textbox, enter the DN of the user that has appropriate access to the Root Sufﬁx / Bind DN in the step above. 10. Enter the Password twice for the user speciﬁed in the step above. 11. Click the Test button to verify that you can properly bind to the Bind DN. 12. Assuming you entered the correct information, a Test Successful! message will appear. Click the OK button. 13. Click the OK button on the next page and you will be asked if you would like to save Join Users. Click the Yes button and the Bind DN you speciﬁed will appear. 14. You can now browse the newly created branch and verify that attributes of users from both Directory 1 and 2 are included in the branch. 5 Appendix A - Run VDS as a Windows Service VDS can be run as a windows service. To do so, run the service.bat ﬁle located in the root of your VDS installation. The idea is that you ﬁrst create a conﬁguration ﬁle, using the GUI and once you’re satisﬁed with it you run the VDS as a service. The conﬁguration ﬁle should have the "ldif" extension and be located in the "local" directory of your installation. So if you have, say, the conﬁguration ﬁle "myconf.ldif" in the "local" directory then you can install the service that uses that conﬁguration by running service.bat install myconf in the installation directory. This will install the "Symlabs Directory Extender 3.5 (myconf.ldif)". To start or stop the service use your Windows Services interface. The logs for the service will be stored in the logs directory of your installation. To remove the service run service.bat remove myconf. If you decide to uninstall DE, be sure to ﬁrst remove any services that you may have installed. August 15, 2007 Todd Schwind (todd@symlabs.com) Getting Started, page 36