Project

General

Profile

Actions

Bug #3679

closed

Generated passwords don't substitute

Added by krileon over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
06 September 2012
Due date:
% Done:

100%

Estimated time:

Description

When using randomly generated passwords they don't substitute as only the password sent with POST is substituted, which when using randomly generated nothing is sent with the POST. An if check needs to be added that if no password is sent with POST then just add user object password.

https://www.joomlapolis.com/forum/153-professional-member-support/209282-auto-login-and-auto-password-generation?limit=6&start=6

Actions #1

Updated by krileon over 11 years ago

  • Target version set to 3.1.0
Actions #2

Updated by krileon over 11 years ago

Both raw password and user object password are completely empty at onAfterUserRegistration trigger.

Actions #3

Updated by krileon over 11 years ago

Password is set in object just fine in cb.tables. Somewhere before it reaches CB Auto Actions it's lost somehow.

Actions #4

Updated by krileon over 11 years ago

Found it, object password is forced null in CB Auto Actions; simply needs removed. This will of course, depending on trigger, result in encrypted passwords being substituted, but that's fine and is better then null or [password] showing.

Actions #5

Updated by krileon over 11 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by krileon over 11 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF