[FIX] Events API user hashes placed in wrong location (LRN-51428)#45
Merged
Merged
Conversation
danny-beton-lrn
requested review from
georgios-kanellopoulos-lrn and
michael-linnane-lrn
as code owners
georgios-kanellopoulos-lrn
approved these changes
Jun 26, 2026
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
2 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
The Events API user hashes were being placed in
security.usersinstead ofconfig.users. This caused 403 errors when the client tried to subscribe to event topics, because the event bus couldn't find the authentication hashes where it expected them.Changes
index.jsto place hashed users in the request object (output asconfig.users) instead of the security packetTesting