Tickets :: [#3420] Allow signup hooks to overwrite username and password fields

6.0.0-beta1

7/29/25

Summary	Allow signup hooks to overwrite username and password fields
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	Horde Developers (at)
Requester	thomas (at) gelf (dot) net
Created	02/07/2006 (7112 days ago)
Due
Updated	05/13/2007 (6652 days ago)
Assigned	02/07/2006 (7112 days ago)
Resolved	05/13/2007 (6652 days ago)
Milestone
Patch	Yes

05/13/2007 04:09:00 AM	Chuck Hagenbuch	Comment #5 State ⇒ Resolved	Reply to this comment
Duplicate of ~~request 2904~~. :)

02/07/2006 02:55:08 PM	thomas (at) gelf (dot) net	Comment #4	Reply to this comment
:-)

02/07/2006 02:47:45 PM	Jan Schneider	Comment #3 Summary ⇒ Allow signup hooks to overwrite username and password fields	Reply to this comment
Wow, nice way to disclose Bcc recipients.

02/07/2006 02:43:54 PM	Jan Schneider	Assigned to Horde Developers

02/07/2006 02:43:12 PM	Jan Schneider	Summary ⇒ Allow signup hooks to overwrite username and password fields State ⇒ Assigned

02/07/2006 02:37:06 PM	thomas (at) gelf (dot) net	Comment #2	Reply to this comment
Subject should be changed to "Allow signup hooks to overwrite username and password fields"...

02/07/2006 02:29:27 PM	thomas (at) gelf (dot) net	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Allow hooks to overwrite username and password fields Queue ⇒ Horde Framework Packages New Attachment: horde_signup_hook.diff State ⇒ New	Reply to this comment
People might want to use a custom field order or a custom field description in their Signup-Forms. This patch checks if such fields (user_name and password) are supplied by _horde_hook_signup_getextra() and if so, HordeSignupForm uses them instead of it's own fields. Same thing happens to horde/admin/user.php. Patch isn't against CVS-HEAD but against H3.1-rc1 so path names may need to be changed. Sorry for this - I'm in a hurry right now... Cheers, Thomas Gelf