•  
     
    story #29981 restrict an OnlyOffice server to some projects only
Summary
Empty
restrict an OnlyOffice server to some projects only

different organization can pay licenses on their own

Bottom line: one project can only have one ONLYOFFICE server and the project itself doesn't have to be aware of that. It's site administrator stuff.

Configuration is done by site administrator:

  • By default, there is only one ONLYOFFICE server and it is available to all platform.
  • I can restrict usage of server to a subset of projects
  • When I create new ONLYOFFICE servers (in addition to the first one) they are "closed" by default, it means that I need to add new projects explicitly
  • When there are several ONLYOFFICE servers defined
    • they must be restricted
    • at project creation, new project doesn't have ONLYOFFICE integreation, it must be added manually to one of the approved server

Edge cases:

  • Given I have 2 ONLYOFFICE servers (hence restricted) and I remove one. The other stay restricted.
Empty
Empty
Status
Doc/Documentation manager
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#29981
Manuel Vacelet (vaceletm)
2023-01-23 18:16
2022-12-09 16:16
3664

References
Referencing story #29981

Git commit

tuleap/tuleap/stable

feat: Introduce table to manage OO servers 51125153c1
feat: Remove usage of config-set for OO server settings 302eda6df3
feat: Ability to remove a document server fef94131c6
refactor: do not store anymore settings in forgeconfig 9033992795
refactor: tie save token to a specific server 4b930e7df5
Bump ONLYOFFICE document server from 7.2.0.204 to 7.2.1.34 aad725512c
Put infrastructure in place to restrict access to a OO document server to some projects 9f9e629a60
fix: ArgumentTypeCoercion psalm error 7e87fae4e4
Add missing happy path test 3b0e7454dc
feat: Initiate display of project restrictions 63fd700c2e
Wrap DocumentServerDao::retrieveAll in a transaction fc8b287b2b
feat: autocompleter for project to allow 1c1665e4c8
feat: Add (virtually) project in the allowed projects c7602cccb4
feat: Filter allowed projects table 746079fb74
feat: Remove (virtually) access to a server 3503289bbe
feat: Display indication on which project is being allowed 4da8fc6089
feat: Save allowed/revoked projects 6a85eca0bc
fix: Display project icon in allowed projects table f4cd0e0bd3
test: Add assertion for project restrictions after server deletion 6cc1d3e328
Refactor: convert restrict modal to dedicated view 680a6815d4
feat: Use badge instead of code for server url 39d2f58c7c
feat: Unrestrict server c58d8cf4de
feat: Always display "allow all" switch d7c66acf1a
feat: Restrict server 1929326290
Remove the possibility to restrict the ONLYOFFICE plugin to some projects 3eccb9b7f0
feat: Create more than one server b93d8aaf8a
ONLYOFFICE server project restrictions are not taken into account correctly 31fb619d02
feat: Reduce nb click when adding/removing projects 7207fa2ef2
fix: Design adjustments 5b3e8290f5

Follow-ups

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes