OpenSolaris

Printable Version Enter a New Search
Bug ID 4942874
Synopsis RFE: native ldap client with ssl restricted to ports 636/389
State 10-Fix Delivered (Fix available in build)
Category:Subcategory ldap:switch
Keywords duckwater | dwp0 | sparks
Responsible Engineer Tomas Heran
Reported Against 5.1 , 5.8 , 5.9 , s10 , s81 , 5.10 , s28_38 , snv_70 , solaris_9 , s28_38shwp , solaris_10 , s81_58shwpl3
Duplicate Of
Introduced In solaris_9
Commit to Fix snv_93
Fixed In snv_93
Release Fixed solaris_nevada(snv_93)
Related Bugs 6262428 , 6262442 , 6573399 , 6646247 , 6711290 , 6711292 , 6712098 , 4880322
Submit Date 23-October-2003
Last Update Date 3-July-2008
Description
Per

http://docs.sun.com/db/doc/806-4077/6jd6blbe5?a=view#ldapsecure-66
Note - 
In order to use TLS for the Solaris LDAP naming service, the directory server must use the default ports, 389 and 636, for
LDAP and SSL, respectively. If your directory server does not use these ports, you cannot use TLS at this time.


Request for enhancement to allow the support of other ports instead
of 636/389.

This restriction makes the assumtion that all customers who plan to
migrate to native ldap in a secure environment  plan to
use a single instance of DS on the machine which in many instances
is completely not true.  It minimizes the scaleability of the ldap
server by imposing this restriction.
Work Around
N/A
Comments
N/A