Directory Server relies on the Network Security Services, NSS, layer for cryptographic algorithms. NSS has been validated to work with the Sun cryptographic framework provided on Solaris 10 systems, which supports cryptographic acceleration devices.
On Microsoft Windows systems, Directory Server requires ActivePerl software to use account activation and manual schema replication commands. Directory Server Enterprise Edition does not provide ActivePerl. The dependency concerns the following commands.
On Microsoft Windows systems, you must disable the pop-up blocker to make Directory Service Control Center work properly.
The Directory Service Control Center supports the following application servers:
Sun Java System Application Server 8.2.
Tomcat 5.5.
For more information, see Installing Directory Service Control Center From Zip Distribution in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.
Directory Proxy Server will work with any LDAPv3 compliant directory servers, but it is tested only with Sun Java System Directory Server.
For virtualization, Directory Proxy Server has been validated with the following JDBC data sources, using the drivers mentioned below.
JDBC Data Source |
JDBC Driver |
---|---|
DB2 v9 |
IBM DB2 JDBC Universal Driver Architecture 2.10.27 |
JavaDB 10.2.2.0 |
Apache Derby Network Client JDBC Driver 10.2.2.0 |
Microsoft SQL Server 2005 |
sqljdbc.jar 1.2.2323.101 |
MySQL 5.0 |
MySQL-AB JDBC Driver mysql-connector-java-5.0.4 |
Oracle 9i DatabaseOracle 10g Database |
Oracle JDBC driver 10.2.0.2.0 |
On Microsoft Windows systems, the dsee_deploy command cannot properly register software with the Common Agent Container, cacao, when you run the command from an MKS shell. This can occur when your MKS PATH does not include the system-drive:\system32 folder. Alternatively, run the command on the Microsoft Windows native command line.
On Solaris 10, rc.scripts are deprecated so commands like dsadm autostart are not supported. Instead use Solaris 10 Service Management Facility (SMF) to handle these types of requests. For example, dsadm enable-service. For more information on SMF, see the Solaris operating system documentation.
All connectors must be able to communicate with Message Queue.
In addition, the following connector requirements must be met.
The Active Directory connector must be able to access the Active Directory Domain Controller over LDAP, port 389, or LDAPS, port 636.
The Directory Server connector must be able to access Directory Server instances over LDAP, default port 389, or LDAPS, default port 636.
Each Directory Server plug-in must be able to reach the Directory Server connector’s server port, which was chosen when the connector was installed. Plug-ins that run in Directory Server Master replicas must be able to connect to Active Directory’s LDAP, port 389, or LDAPS, port 636. The plug-ins that run in other Directory Server replicas must be able to reach the master Directory Server LDAP and LDAPS ports.
The following table displays the browsers for each operating system that supports Directory Service Control Center.
Operating System |
Supported Browser |
---|---|
Solaris 10 and Solaris 9 (SPARC and x86) |
NetscapeTM Communicator 7.1, MozillaTM 1.7.12, and Firefox 1.0.7, 1.5, and 2.0 |
Red Hat Linux 4, Red Hat Linux 3 and SuSE Linux |
Mozilla 1.7.12 and Firefox 1.0.7, 1.5, and 2.0 |
Windows XP |
Netscape Communicator 8.0.4, Microsoft Internet Explorer 6.0SP2 and 7.0, Mozilla 1.7.12, and Firefox 1.0.7, 1.5, and 2.0 |
Windows 2000/2003 |
Netscape Communicator 8.0.4, Microsoft Internet Explorer 6.0 SP1 and 7.0, Mozilla 1.7.12, and Firefox 1.0.7, 1.5, and 2.0 |