The following table gives you information about different options in the iFolder installation---and will help you understand and prepare for the different kinds of information that you must provide during the installation.
| Options | Information |
|---|---|
Apache |
iFolder uses the Apache Web server. To learn more about how Apache and iFolder work together, see Apache and iFolder. IMPORTANT: If you are installing iFolder on a NetWare 6 server and are planning to share an IP address between Apache Web Server and Enterprise Web Server, then change the default iFolder ports during the installation. If you match this criterion, but do not select this option, Apache and iFolder might not load properly. For more information, see the next section iFolder Ports. |
iFolder Ports |
Because iFolder uses the same ports (HTTP nonsecure port 80 and HTTPS secure port 443) as other Web services on NetWare (specifically NetWare Enterprise Web Server), when you install iFolder you must do one of the following:
The nonsecure port is used to send the encrypted username and password and data from the iFolder client to the iFolder server. iFolder uses RSA* encryption to encrypt the username and password, and Blowfish* encryption to encrypt the user data. The secure port is used to access the iFolder Management Console and the Java applet via SSL and HTTPS. |
Global LDAP Settings |
Global LDAP settings identify the LDAP host that will be used to manage the iFolder servers. For basic information on LDAP and how it works with the iFolder architecture, see LDAP and iFolder. IMPORTANT: If you are installing more than one iFolder server, use the same Global LDAP Settings for all iFolder servers, otherwise, iFolder will not function properly. |
LDAP Ports |
Choose port 389 if you want to use LDAP without SSL encryption or if your LDAP server does not support SSL. Port 389 is also a good choice if iFolder and LDAP are running on the same server (no communication or data is being transferred across the wire, so no encryption is necessary). If you are using port 389, the LDAP Group object must be marked to Allow Clear Text Passwords. To verify this, launch ConsoleOne® and locate the context where your server resides, right-click the LDAP Group object, click Properties, and check Allow Clear Text Passwords. Choose port 636 if you want to use SSL, which provides your network with encryption and security when data is transferred across the wire. If you choose port 636, make sure you have copied the ROOTCERT.DER file from your LDAP server's SYS:PUBLIC directory to your iFolder server SYS:PUBLIC directory prior to the iFolder installation. If you choose port 636, you must enter the path to the LDAP trusted root certificate. This will be the path to the SYS:PUBLIC directory where you copied ROOTCERT.DER prior to the installation. For more information, see General Server Requirements. |
LDAP Login DN Context |
This is the context of the container where your Admin objects are located. This is also where the iFolder server and LDAP objects will be created. For more information on these objects, see Logging In to the iFolder Management Console. iFolder allows you to enter multiple contexts. After each context, insert a semicolon (;). Do not put any spaces between the contexts. HINT: Previoiusly, you needed to specify the LDAP user context during the installation. Now, you specify your user context by modifying your Global Settings after the iFolder installation is complete. For more information, see Defining Your User Context. |
Admin Names |
Enter the names of all administrators who need rights to modify iFolder user account information via the Server Management Console. Administrators must have user accounts in your LDAP directory as well as Supervisor rights to the LDAP directory. If you are entering more than one name, separate the usernames with a semicolon, not spaces. For example, if you wanted John Smith and user Admin to have rights to administer the Server Management Console, you would enter admin;jsmith. IMPORTANT: At least one of the Admin users that you list must exist in a container in the LDAP Login DN Context. Usernames whose objects are located outside this context will not be able to access and use the Global Setting section of the iFolder Management Console. Also, Admins will need rights to add attributes to eDirectory objects if they want to use the User Management section of the iFolder Management Console. |