Closed
Bug 541983
Opened 15 years ago
Closed 15 years ago
Set up Live Chat login migration on chat-support-stage.mozilla.com
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: zzxc, Assigned: oremj)
References
Details
After TikiWiki is set up (bug 541982), Openfire must be updated to complete testing.
This will require switching from running an Openfire package from igniterealtime.org to running our own build. Instructions to set this up:
# Uninstall the Openfire RPM to avoid conflicts between the two versions.
# Build Openfire by following the steps at https://wiki.mozilla.org/Support/Live_Chat/Building
# Update openfire.xml by filling in the TikiWiki database host, name, username, and password.
# Start Openfire by executing ./target/openfire/bin/openfire.sh
# Once this build is working properly, change the startup script to execute Openfire on booting
# Edit the cron job that restarts Openfire every Sunday to restart the custom build instead of using the init.d script
Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → jeremy.orem+bugs
Comment 1•15 years ago
|
||
This is still blocking me from testing the Live Chat integration/migration: https://wiki.mozilla.org/Support/Live_Chat/SUMO_login/Testing.
Can we please get this resolved ASAP? Thanks!
Severity: major → critical
Assignee | ||
Updated•15 years ago
|
Whiteboard: Blocked on broken java download.
Assignee | ||
Comment 2•15 years ago
|
||
It's running. I have no idea how to tell if it is working. When we roll this in to production it'd be nice if you could take the openfire src rpm and build a new rpm with all this stuff.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Whiteboard: Blocked on broken java download.
Comment 3•15 years ago
|
||
https://chat-support-stage.mozilla.com:9091/plugins/registration/sign-up.jsp is timing out for me.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•15 years ago
|
||
Update: oremj told me to use http://chat-support-stage.mozilla.com:9091/plugins/registration/sign-up.jsp instead (which I've done), but Matthew said he'll need to build some plugin (iirc) and copy a few things from sumotools, so I can create a test account on chat-support-stage.mozilla.com (right now it's just the login screen).
Updated•15 years ago
|
Whiteboard: [waiting on middleton]
Assignee | ||
Comment 5•15 years ago
|
||
Anything left on this?
Comment 6•15 years ago
|
||
(In reply to comment #5)
> Anything left on this?
Given that bug 543115 just (re)landed, I think we'll need to go through all the IT bugs linked in the tracking bug (including this one), and re-run those steps. Thanks!
Reporter | ||
Comment 7•15 years ago
|
||
I built the Openfire trunk code into an RPM, which is in my home folder on sumotools:
/home/zzxc/sumo151-rpm/openfire.sumo151.build1.rpm
This needs to be deployed to chat-support-stage ASAP, so testing the login migration can continue.
Assignee | ||
Comment 8•15 years ago
|
||
rpm has been installed. Is everything working?
Assignee | ||
Updated•15 years ago
|
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•15 years ago
|
||
There is a new RPM to pick up the patch for bug 544934, again on sumotools at /home/zzxc/sumo151-rpm/openfire.sumo151.build2.rpm
Once this is installed, the only remaining step is to switch on login migration - which I can do from the admin panel. For the record, here are the steps to do that:
1) Log into the admin panel at http://chat-support-stage.mozilla.com:9091
2) In the Server tab, choose System Properties
3) Set all of these properties:
*provider.auth.className: org.mozilla.support.sumologin.SumoAuthProvider
*provider.authorizationMapping.classList: org.mozilla.support.sumologin.SumoAuthorizationMapping
*provider.authorization.classList: org.mozilla.support.sumologin.SumoAuthorizationPolicy
*provider.user.className: org.mozilla.support.sumologin.SumoUserProvider
*provider.group.className: org.mozilla.support.sumologin.SumoGroupProvider
*sumologin.jdbc.connectionString: jdbc:mysql://localhost/dbname?user=username&password=secret (use the SUMO stage database setting here)
*sumologin.migrationStatus: 1
*sumologin.reminderText: Please visit the migration page to migrate your account
4) restart Openfire
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Jeremy, do you have time to work on this today? It's blocking SUMO's 1.5.1 release; thanks!
Assignee | ||
Comment 11•15 years ago
|
||
I've installed the new rpm. I assume anyone can log in and do the web admin tasks.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 12•15 years ago
|
||
I configured everything except for sumologin.jdbc.connectionString, which I don't have the database information for. Could the database connection information (host, dbname, user, pass) be added to a file that I can access on sumotools?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 13•15 years ago
|
||
After discussing this with justdave, I changed the database settings to be stored in openfire.xml instead of in the admin panel. I wrote a patch to do this in bug 545947, which I included in a new RPM.
The new RPM (/home/zzxc/sumo151-rpm/openfire.sumo151.build3.rpm) should be installed on chat-support-stage, and the following section needs added to openfire.xml inside <jive/>.
<sumologin>
<jdbc>
<connectionString>jdbc:mysql://HOSTNAME/DATABASENAME?user=USERNAME&password=PASSWORDTHATHASBEENURIENCODEDIFNECESSARY</connectionString>
</jdbc>
</sumologin>
Matthew: can we still proceed with testing?
https://bugzilla.mozilla.org/show_bug.cgi?id=545947#c2 seems to indicate so, but I want it to be patently clear; thanks!
Reporter | ||
Comment 15•15 years ago
|
||
(In reply to comment #14)
> Matthew: can we still proceed with testing?
Migration is currently turned off on staging, and a server restart is needed to turn it on. Testing can continue after either the instructions in either comment 12 or comment 13 (not both) are finished and the server is restarted. From my discussion with IT, comment 13 seems to be the preferred option.
Assignee | ||
Comment 16•15 years ago
|
||
New rpm has been installed and I've added the connection string.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 17•15 years ago
|
||
Migrated accounts and groups are now showing up at http://chat-support-stage.mozilla.com:9091/group-summary.jsp , so the database setting too effect. Thanks!
->Verified.
Status: RESOLVED → VERIFIED
Whiteboard: [waiting on middleton]
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•