mahara-contributors team mailing list archive

[John <855525@xxxxxxxxxxxxxxxxxx>]

Hi Piers, I cannot change the LDAP/AD structure and all our other
systems have a list of LDAP servers which they try in order until a
match is found or none. If the first fails, they use the next. I can
understand having the institute in the user details but not a particular
server. I might be wrong, but it looks like Mahara does try each one in
turn by priory and  therefore the first successful lookup must be the
server in the user details. If it isn't you will get an error message
even though you have entered the correct username and password. This is
a bad design and counter intuitive.

John.

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

Title:
  Logon failure - LDAP authentication tied to one server

Status in Mahara ePortfolio:
  Won't Fix

Bug description:
  Mahara 1.4.0
  Linux Centos 5.7
  MySQL
  All browsers

  User logons failing when username and password are correct.

  We added two new Microsoft AD servers to our institution. However, all
  accounts in this institution cannot logon using these servers due to
  the users having the auth_instance declared in their usr entry
  (authinstance). If I update the auth_instance with the new server
  details they can logon. This means if that server fails users will not
  be able to logon even though we have other servers listed which can
  authenticate.

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