Skip to content

feat: propagate userName through CallContext authentication#97

Closed
shilenkoalexander wants to merge 2 commits intomasterfrom
oshy/STL-2406-user-name-in-gdc-context
Closed

feat: propagate userName through CallContext authentication#97
shilenkoalexander wants to merge 2 commits intomasterfrom
oshy/STL-2406-user-name-in-gdc-context

Conversation

@shilenkoalexander
Copy link
Copy Markdown
Contributor

Summary

  • Add userName: String? = null field to CallContextAuth data class
  • Wire userName from CallContextAuth through CallContextAuthenticationProcessor into the user context (previously hardcoded to null)
  • Add test verifying userName propagation in CallContextAuthenticationProcessorTest

Context

Part of STL-2406: gateway now sets the user's display name in the gdc-context header (UserContext.name). This change ensures the name flows through CallContextAuth into AuthContext in downstream services.

🤖 Generated with Claude Code

shilenkoalexander and others added 2 commits March 3, 2026 16:18
… has authMethod=JWT STL-2167

When gd-call-context header contains "authMethod":"JWT", the gateway has already validated
the JWT token. BearerTokenReactiveAuthenticationManagerResolver now returns a no-op manager
in this case to skip redundant re-validation that would fail downstream.

Also update existing BearerTokenReactiveAuthenticationManagerResolverTest mocks to stub
the gd-call-context header lookup added by the new guard check.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add userName field to CallContextAuth and wire it through
CallContextAuthenticationProcessor so the user's display name
set by the gateway is available in downstream AuthContext.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@shilenkoalexander shilenkoalexander deleted the oshy/STL-2406-user-name-in-gdc-context branch March 30, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant