The tools of a digital workplace rarely talk to each other. A document lives in Nextcloud, but you need to link it in a task, a ticket, or a wiki article. Until now that meant: copy the share link, switch apps, paste. The SecTepe platform (SecTepe.Comm) removes this gap. It adds a ☁ Nextcloud button right in the editor of six apps.
Six Apps, Six Editor Technologies
The button sits in the text editors of six very different apps. You pick a file, and the permalink lands where your cursor is:
- Vikunja (tasks): TipTap/ProseMirror,
- Redmine (project management): textarea with jstoolbar, Markdown or Textile,
- Wiki.js (knowledge): CodeMirror 5/6 and CKEditor 5,
- Moodle (learning): TinyMCE and Atto,
- TheHive (SOC cases): Markdown textarea,
- Zammad (support): its own contenteditable.
The Truly Hard Problem
All six are upstream images with no frontend plugin system. And none of them holds the Keycloak token that Nextcloud needs. The fix is simple on purpose:
- one shared script with an adapter for each editor,
- injected with nginx
sub_filterjust before the closing</head>, - plus a matching Traefik route.
This way the link works without forking the upstream apps.
Same-Origin, OAuth2, and Strictly Read-Only
Nextcloud is reached same-origin through /_sectepe/nc/. There, oauth2-forwardauth sets the Keycloak bearer token, and Nextcloud checks it with user_oidc. Access is strictly read-only. It uses only OCS user info and PROPFIND, with no public share links. So the permalink always leads into Nextcloud with its normal access rights. It never makes content public by accident.
A Sovereign Digital Workplace in Practice
This feature is a clear example of what SecTepe.Comm aims to be: a sovereign communication platform. It is not one more silo. It is a set of open-source building blocks that work together under one shared identity. Removing small points of friction in daily work often wins users over more than long feature lists.
Conclusion
One ☁ button in six apps, same-origin and strictly read-only. The Nextcloud link turns scattered tools into one workplace. It needs no upstream forks, and it does not weaken security. That is what sovereign integration looks like in practice.