[Yanel-dev] [Bug 8228] Add "alias" to user interface for creating a new user

[bugzilla at wyona.com]

http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=8228





------- Comment #3 from ioannis at wyona.com  2011-03-31 18:38 -------
Created an attachment (id=1400)
 --> (http://bugzilla.wyona.com/cgi-bin/bugzilla/attachment.cgi?id=1400&action=view)
proposed fix for creating an alias

"Review and Then Commit" as described in
-- http://localhost:8080/yanel/yanel-website/en/development/processes/rtc.html

Does it build?  Yes
Is the formatting correct? Yes

Is it backwards compatible?     Yes
-- Because the two new fields in the create new user form are optional, so any
existing canoo web-tests will still pass.
-- The CreateUserResource.java class that handles the request simply checks if
those fields are set and if they are it calls the existing method
UserManager.createAlias().
-- If these fields are absent in an older implementation, their corresponding
parameters are not set and the class gracefully ignores them.

Does it scale/perform? (Can the implementation be changed?)     Yes
Can it be enhanced?     Yes
Can it be customized?   Yes
Does it work within a cluster   ?
-- Must make the UserManager.createUser() method synchronized to ensure userID
remain unique.

Is it secure    ?
-- No method exists in UserManager to check whether an alias already exists. It
is possible to create identical aliases in different accounts. Serious issue. 
Can it be used Yes
-- I have tested it, creating a new user and confirming the entry in the list
of users

Can the patch be reverted easily        ?
Does an automatic test exist? No
-- I have tested in myself however, creating a new user and confirming the 

Does it work for all browsers   ?
Only tested in Firefox 3. However html change was trivial, following the
pattern of the existing markup. So in the least it should carry on working for
the existing set of browsers.


-- 
Configure bugmail: http://bugzilla.wyona.com/cgi-bin/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.