[JS2-213] Adding a User with an invalid password creates the user (without password) although an error is reported

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0-dev/cvs
• Fix Version/s: 2.0-dev/cvs, 2.0-M2
• Component/s: Admin Portlets, Persistence and DAO, Security
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 16/Feb/05 07:33
• Updated: 28/Mar/05 08:40
• Resolved: 28/Mar/05 08:40

Description

When a User is added with an invalid password (we use the SimplePasswordCredentialValidator) using the User Admin Portlet
an error message is reported that the user cannot be created (just that...).
When subsequently a correct password is entered and adding the user is tried again the error: User is already defined
is reported back although the user isn't visible (yet) in the the list above.
Only after logging on again (or adding another user successfully) the created user is displayed. This is a caching problem.

A SECURITY_PRINCIPAL record is created but without a SECURITY_CREDENTIAL record.
To solve this problem, the user should not be created when the supplied password is invalid.