feat(fleet): WhoAmI RPC returning the verified operator identity#44
Merged
Conversation
This was referenced Jul 14, 2026
Merged
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.
What and why
Adds
FleetService.WhoAmI+ anOperatorIdentitymessage so the Fleet Manager can echo the operator identity it verified from the presented mTLS client certificate (subject CN, cert serial, access level). The browser cannot read its own installed client cert, so the manager needs an endpoint that returns the verified identity/level for role-aware UI (Slice A).Regenerated Go + TS via buf; only the proto and generated files changed.
Closes #43
Verification
How this was verified
Inspected the proto diff (RPC added last in FleetService; WhoAmIRequest/OperatorIdentity/WhoAmIResponse appended, no field renumbering) and confirmed
WhoAmIappears in the generatedfleetv1connect.FleetServiceHandlerinterface and client. Merge order: this lands first; the manager then bumps to consume it.