fix: pass X-User-Id header in M2M API calls#9
Merged
raghavyuva merged 1 commit intomainfrom Apr 8, 2026
Merged
Conversation
Forward the triggering user's ID from requestContext to the Nixopus API so M2M-authenticated requests carry proper user context.
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
1 participant
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
requestContextas anX-User-Idheader when making M2M-authenticated API calls to Nixopus, enabling proper user context on the API side.Test plan
fix/m2m-user-context-passthrough)X-User-Idheader is present in outbound requests whenuserIdis in the request context