1d707ba5f0 Fix gRPC context propagation in AuthServiceImpl (#4960)
The userId was being read inside the Future block, which runs on a
thread from ExecutionContext.global. However, gRPC Context.current
returns the context for the current thread, not the gRPC handler
thread where the JWT claims were attached.

This caused setDisplayName and getCurrentUser to always get null/empty
userId, resulting in "User not found" errors after successful OAuth.

Fix by capturing userId before creating the Future, on the gRPC thread
where Context.current has the proper claims attached. This matches
the pattern used in EagleServiceImpl.lockAndDoWithUserName.

Also update AuthorizationInterceptor publicEndpoints to use
CheckOAuthStatus instead of the old ExchangeCode method name.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-01 15:19:41 -08:00
2025-03-30 11:19:46 -07:00
2025-09-24 08:13:22 -07:00
2014-11-16 21:03:14 -08:00
S
Description
No description provided
Readme
9.4 GiB
Languages
Scala 44.5%
C++ 19.9%
C# 16.6%
Starlark 10.1%
Go 3.5%
Other 5.3%