mahara-contributors team mailing list archive

[Mahara Bot <812057@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/486
Committed: http://gitorious.org/mahara/mahara/commit/a6c7e9856377e06c1b0ca652f380ee692924406c
Submitter: Hugh Davenport (hugh@xxxxxxxxxxxxxxx)
Branch:    master

commit a6c7e9856377e06c1b0ca652f380ee692924406c
Author: Hugh Davenport <hugh@xxxxxxxxxxxxxxx>
Date:   Mon Jul 18 11:13:33 2011 +1200

    Allow specifying alternate port for ldap servers
    
    Allows you to specify a host_url such as
    ldapserver:1025
    to allow you to connect with the ldap server on port 1025
    
    Also works with hosts prefixed with ldap:// and ldaps://
    
    Bug #812057
    
    Change-Id: I560c7e37df2c716b9be092150605b2ad51b97dea
    Signed-off-by: Hugh Davenport <hugh@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/812057

Title:
  ldap auth plugin doesn't allow alternate ports

Status in Mahara ePortfolio:
  Fix Committed

Bug description:
  This is probably two problems, one with php, and one with mahara.
  If you specify a host url as ldaps://ldapserver you would expect it to connect to port 636, but instead it tries the default for ldap 389.
  I thought you would be able to specify a hosturl as ldaps://ldapserver:636 to specify a port, but mahara doesn't parse this and call the connect function properly

  I will submit a fix to the second issue first, but do people think it
  is worth filing a bug upstream to php about not choosing 636 as
  default for ldaps

  Cheers,

  Hugh

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/812057/+subscriptions