mahara-contributors team mailing list archive

[Aaron Wells <1045123@xxxxxxxxxxxxxxxxxx>]

Another scenario when the password field has come in handy for me, was
during a support call by a client doing Mahara training. Her students
were supposed to have registered their Mahara accounts prior to the
class, but there were a couple who hadn't, and so I needed to create
accounts for them and give them their login info over the phone, because
the class was in progress and it was essential to get it done fast
without having to wait to check emails.

So I think we should leave the password field as an option, but have it
be disabled by default. Like, have a checkbox that says "manually assign
password?" (unticked by default) and when it is unticked the password
field is grayed out. That will encourage admins to use the email
confirmation process instead, while still leaving the manual password
process as an option when needed.

Cheers,
Aaron

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1045123

Title:
  don't send out password for admin created users

Status in Mahara ePortfolio:
  Triaged

Bug description:
  When an admin creates a user with a set password. It should be assumed that this password is delivered to the user out of band, and shouldn't be sent in clear text.
  If the password field is left blank, we should treat that the same as if we just finished a registration, the user gets a one time URL to click on which forces them to set a password.

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