mahara-contributors team mailing list archive

[Richard Mansfield <633273@xxxxxxxxxxxxxxxxxx>]

Hi Ruslan,

It doesn't really gain much over just changing the user's regular mahara
username to be the same as the LDAP username (anyone who logs in at the
mahara login form needs a unique username anyway).  So it'd be easier to
just give the admin the power to change the mahara username for anyone
who's using LDAP auth.  I hope LDAP users are already prevented from
changing their own usernames.

Having said that, there is another case I'm aware of where it could be
worth using that external auth username even for users who log in at the
mahara login form.  Check out this bug:
https://bugs.launchpad.net/mahara/+bug/548165

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

Title:
  Changing username for external authentication does not change Mahara username 

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  1.3.0cr,  PostgreSQL 

Our institution is using LDAP authentication for the Mahara application.  When faculty do not yet have a NetID, I had hoped to register them in with a temp ID, and use the internal authentication.  Later, when they recieved a NetID, I would change their username to the new NetID and change authentication type to the LDAP.  When I try to do this, the username is saved in the "Username for external authentication", but as Admin, I still see their old (temporary) ID next to their name.  

Is this a bug?  Or, does the initial ID remain in the Mahara database, regardless of the authentication username associated with the account?