Release Notes › Policy Server Release Notes › Defects Fixed in SiteMinder Releases › Defects Fixed for 6.0 SP5 › SiteMinder using LDAP Referral over SSL fails to connect when the Port Number is not Part of the Referred URL (52425)

Previous Topic: Policy Resolution Fails When a RADIUS Agent Group is Configured for a Realm (52371)

Next Topic: LDAP Filter Generated using the LDAP Expression Editor Displays a Syntax Error in the smps log (52687)
SiteMinder using LDAP Referral over SSL fails to connect when the Port Number is not Part of the Referred URL (52425)

When using referred URL containing LDAPS, it was being sent to the referred server on non-SSL port 389 instead of SSL port 636. This is no longer an issue. The force assignment of 389 as the port number is disabled for all cases when port is not mentioned in the referred URL. The secure option of the parsed URL is verified and the port 389 or 636 is set accordingly.