Skip to content
Best Practices

Link Nextcloud Files Directly in Six Applications

SecTepe Editorial
|
|
6 min read

Between the tools of the digital workplace there is usually a quiet break in media: a document lives in Nextcloud, but it has to be linked in a task, a ticket, a wiki article. Until now that meant: copy the share link, switch apps, paste. The SecTepe platform (SecTepe.Comm) removes this break with a ☁ Nextcloud button right in the editor of six applications.

Six Apps, Six Editor Technologies

The button is available in the text editors of six very different applications – pick a file, the permalink lands at the cursor position:

  • 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 Genuinely Hard Problem

All six are upstream images with no frontend plugin system, and none of them holds the Keycloak token that Nextcloud needs. The solution is deliberately pragmatic: one shared script with editor-specific adapters, injected via nginx sub_filter before the closing </head>, plus a matching Traefik route. This makes the integration work without forking the upstream applications.

Same-Origin, OAuth2, and Strictly Read-Only

Nextcloud access is same-origin via /_sectepe/nc/, where oauth2-forwardauth sets the Keycloak bearer token; Nextcloud validates it via user_oidc. Access is strictly read-only – only OCS user info and PROPFIND, no public share links. The linked permalink thus always leads into the permission-based Nextcloud instead of inadvertently making content public.

A Sovereign Digital Workplace, Made Concrete

This linking is a tangible example of the ambition of SecTepe.Comm as a sovereign communication platform: not another silo but an integrated interplay of open-source building blocks under a shared identity. Removing small friction points in everyday work often decides acceptance more than large feature lists.

Conclusion

A ☁ button in six applications, secured same-origin and strictly read-only: the Nextcloud linking turns scattered tools into a coherent workplace – without upstream forks and without softening security. That is what sovereign integration looks like in practice.