Closed
Bug 1247684
Opened 9 years ago
Closed 9 years ago
Deploy Mozilla Data Classification Confluence plugin in stage
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gene, Unassigned)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2563] )
Attachments
(2 files)
Hi,
Please deploy the attached Mozilla Data Classification Confluence plugin into the staging confluence instance to see if it works.
Since I've not had access to a confluence environment, this plugin is built entirely based off of atlassian docs so I don't know if it will work.
| Reporter | ||
Comment 1•9 years ago
|
||
What's the target completion date for this and who should the ticket be assigned to?
Flags: needinfo?(nmaul)
Comment 2•9 years ago
|
||
This is installed on mana.allizom.org. No idea how to test, let us know if everything looks reasonable.
NOTE: mana.allizom.org appears to be running a newer version of Confluence than mana.mozilla.org is. I don't know why... perhaps a planned upgrade that hasn't been completed.
Flags: needinfo?(nmaul)
Comment 3•9 years ago
|
||
Once I got the app up and working in general, I eventually ran into this scary-sounding message regarding confluence 5.7+ and LDAP group membership:
https://confluence.atlassian.com/doc/confluence-5-7-upgrade-notes-692781383.html#Confluence5.7UpgradeNotes-AggregatedGroupMembership
Fortunately it sounds rather benign in our case, as I doubt we have a lot of users with accounts from multiple auth sources. Any that do will now be considered members of any groups from *both* sources, rather than just the first one as before. This means any such users may gain privileges they don't currently have.
We have 2 auth sources: LDAP and local-Confluence users. I don't know how many there are of the latter... probably at least a couple for the purpose of troubleshooting LDAP failures, but maybe more.
Comment 4•9 years ago
|
||
Yeah, I saw this message when I last upgraded. I believe it doesn't affect us, as we only have one auth source per user. In fact, I think the number of local user accounts is 1 or 2, and I don't think it's currently possible to log in to those accounts, since we have http basic auth in front of confluence, which only allows LDAP users. I used to be able to log into the administrator account by hitting the tomcat server directly on the host at port :8080, but the last time I tried this, I think it redirected me to https://mana.mozilla.org/wiki. We also don't have any local groups, other than the default built-in ones (confluence-users, confluence-admins), which again we don't use, other than the administrator account.
Regarding comment 2, I think both prod and stage are now on 5.9.4 (see the footer at the bottom of either).
| Reporter | ||
Comment 5•9 years ago
|
||
:jakem would it be possible to get admin rights in confluence on stage? I'm having trouble using the plugin (which could be a bug in my code or something else)
| Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(nmaul)
| Reporter | ||
Comment 6•9 years ago
|
||
Here's a slightly updated version of the plugin which I've installed in stage.
Though the plugin works and the macros function, I'm unfortunately stumped on one challenge
https://answers.atlassian.com/questions/38051331/how-do-you-set-noparams-in-a-confluence-user-macro-plugin
which causes the macros to both not show up in the macro suggestions or macro browser (and less importantly, not have an icon)
so we can close this out and I'll work on solving this and then re-request testing in stage later.
Jake, thanks so much for getting the staging mana working and getting me access to it.
Flags: needinfo?(nmaul)
| Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•