Populate editor user identity for co-editing and authorship #149

New issue

Open

opened 2026-04-26 08:19:01 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 08:19:01 +00:00

Member

Every editor session opens as Anonymous because hero_office_server::build_editor_config does not set editorConfig.user. Two practical effects:

Authorship is invisible — collaborators see only Anonymous on cursors and in the comments side panel.
OnlyOffice cannot distinguish concurrent users, so co-editing degrades (multiple users with the same id collapse onto one editing session).

Acceptance

IslandContext already carries enough identity (context_name, plus whatever the host attaches). Map it into editorConfig.user = { id, name } and JWT-sign as part of the config.
create_editor_session RPC accepts an optional user identity; falls back to a stable per-context anonymous if absent.
Two browsers opening the same xlsx with different identities show two distinct cursors with the right names; this becomes the basis of a follow-up co-editing e2e test.

Every editor session opens as `Anonymous` because `hero_office_server::build_editor_config` does not set `editorConfig.user`. Two practical effects: - Authorship is invisible — collaborators see only `Anonymous` on cursors and in the comments side panel. - OnlyOffice cannot distinguish concurrent users, so co-editing degrades (multiple users with the same id collapse onto one editing session). ## Acceptance - `IslandContext` already carries enough identity (`context_name`, plus whatever the host attaches). Map it into `editorConfig.user = { id, name }` and JWT-sign as part of the config. - `create_editor_session` RPC accepts an optional user identity; falls back to a stable per-context anonymous if absent. - Two browsers opening the same xlsx with different identities show two distinct cursors with the right names; this becomes the basis of a follow-up co-editing e2e test.