Transition Technology: Ticket #82: Security: separate sending of username and password

owner, status changed; estimatedhours, billable set

jim — Thu, 19 Aug 2010 13:28:28 GMT

owner changed from jim to ed
estimatedhours set to 0.0
status changed from new to assigned
billable unset

There's no built-in way to send two emails.

However, since the user typed their own password - twice - they don't really need it in the email at all. They can always use the 'forgotten password' option after all.

So, please go to here https://www.transitionnetwork.org/admin/user/settings and edit the "Welcome, no approval required" message as you see fit. I'd remove the password line and change the text to say 'you chose your password during registration.

Reassigning to Ed since he's the one with the user text thing, though can do if needed.

owner changed

ed — Wed, 25 Aug 2010 15:26:41 GMT

owner changed from ed to jim

a bit confused -

why is there a one time login here when they have already set their password?
why are they being asked to re-set their password?

here is the text as it stands:

Hi !username, Thank you for registering at !site. You may log in by clicking on this link or copying and pasting it in your browser: !login_url This is a one-time login, so it can be used only once. After logging in, you will be redirected to !edit_uri so you can change your password. You may also log in to !login_uri using the following username and password: username: !username password: !password

all the best and welcome,

-- !site team

owner changed

jim — Wed, 25 Aug 2010 15:56:00 GMT

owner changed from jim to ed

Yes, it's a mess and shouldn't say half of those things - just a reminder of the username and link to the login page at /user/login and a welcome note should suffice.

LoginToboggan? removes the need for the one-time login, though they still need to validate their email.

priority changed

ed — Wed, 25 Aug 2010 15:58:25 GMT

priority changed from minor to major

OK then I'll remove all the stuff about one time logins - that might nail the validation problem and other user confusion at that point.

bunging up to major so i remember to tweak this in due course...

status changed; resolution, milestone set

ed — Fri, 17 Jun 2011 11:23:33 GMT

status changed from assigned to closed
resolution set to fixed
milestone set to Phase 4

finally got round to sorting this out. closing.