fix: use single auth token for Helix Authorization header - #197
Merged
Conversation
Helix (api.aem.live) only accepts one bearer token in the Authorization header, but multi-connection saves were comma-joining every connection's auth like da-admin does, breaking Helix writes when multiple users had write access. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
bosschaert
approved these changes
Sep 2, 2026
kptdobe
pushed a commit
that referenced
this pull request
Sep 2, 2026
## [1.7.9](v1.7.8...v1.7.9) (2026-09-02) ### Bug Fixes * use single auth token for Helix Authorization header ([#197](#197)) ([1a4f2e1](1a4f2e1))
Contributor
|
🎉 This PR is included in version 1.7.9 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
api.aem.live) only accepts a single bearer token in theAuthorizationheader.persistence.putwas comma-joining every connected user's auth token (as it does for da-admin), which breaks Helix writes whenever more than one user with write access is connected.persistence.putnow branches onisHelixDoc(ydoc.name): for Helix docs it sends just the first connection's auth token; for da-admin docs it keeps the existing dedup + comma-join behavior.Test plan
persistence.put for a Helix doc with multiple connections uses only the first auth (no comma-join)intest/shareddoc.test.js, covering the regression this fix addresses.npm test— 177 passing, coverage 99.68%.npm run lint— clean.🤖 Generated with Claude Code