Public bug reported: 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 ** Affects: mahara Importance: Low Assignee: Hugh Davenport (hugh-catalyst) Status: In Progress ** Changed in: mahara Assignee: (unassigned) => Hugh Davenport (hugh-catalyst) ** Changed in: mahara Importance: Undecided => Low ** Changed in: mahara Status: New => In Progress -- 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: In Progress 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 _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp