Closed
Bug 545822
Opened 15 years ago
Closed 15 years ago
Implement AuthProvider to handle login migration on Openfire
Categories
(support.mozilla.org Graveyard :: Chat, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
1.5.2
People
(Reporter: zzxc, Assigned: zzxc)
References
Details
Attachments
(1 file)
|
45.89 KB,
patch
|
ozten
:
review+
|
Details | Diff | Splinter Review |
This is the Openfire side of the login migration in bug 503215, consisting of an AuthProvider implementation that reads the TikiWiki database.
The attached code is currently on chat-support-stage at http://chat-support-stage.mozilla.com:9091/ , where it can be tested.
Attachment #426641 -
Flags: review?(ozten.bugs)
Comment 1•15 years ago
|
||
Does this block 1.5.1? The milestone is unset, and it's a little unclear, even though it's blocking bug 503215.
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Does this block 1.5.1? The milestone is unset, and it's a little unclear, even
> though it's blocking bug 503215.
Yep, added milestone.
Target Milestone: --- → 1.5.1
| Assignee | ||
Comment 3•15 years ago
|
||
This blocks enabling login migration on production, but it doesn't block the other code in the release. The Openfire update and restart will need to happen once the migration scripts are in place on TikiWiki, as the AuthProvider depends on the TikiWiki database schema update.
This was originally an Openfire plugin, but I moved the code into the main classpath to prevent issues if the plugin is restarted. It's still possible to update this without upgrading Openfire, but doing so would require IT to upload a file. (In any case, this needs to be used with Openfire built from https://svn.mozilla.org/projects/livechat/trunk , as it won't work properly with the build from Jive)
Assignee: nobody → bugs
Comment 4•15 years ago
|
||
(In reply to comment #3)
> as the AuthProvider depends on the TikiWiki database schema update.
You mean the added livechat_id column in the users_users table?
Comment 5•15 years ago
|
||
Comment on attachment 426641 [details] [diff] [review]
SumoAuthProvider implementation for Openfire
Good use of prepared statements.
Good use of Exceptions to catch invalid inputs, states.
Consider breaking 'authenticate' into smaller methods. Line: 135 could be a migrate user method called from authenticate, etc so that no method is longer than a screen or two.
Line 286-294: If any of these options are likely to change, we should break those out into config.
General feedback - Consider using DB result set methods that take the name of the column, instead of the index. We won't have to comment the line, if the SQL adds a parameter you don't have to update the line of code.
Nice work!
Code reviewed w/o testing or applying patch.
Attachment #426641 -
Flags: review?(ozten.bugs) → review+
| Assignee | ||
Comment 6•15 years ago
|
||
This is checked in r62183.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 7•15 years ago
|
||
(In reply to comment #4)
> (In reply to comment #3)
> > as the AuthProvider depends on the TikiWiki database schema update.
> You mean the added livechat_id column in the users_users table?
Yes
Updated•15 years ago
|
Target Milestone: 1.5.1 → 1.5.2
Comment 8•15 years ago
|
||
Verified FIXED; Vishal and I have tested migration (both automated and manually), and it works for us.
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Product: support.mozilla.org → support.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•