Page MenuHomePhabricator

[identity] verify user access token

Authored by varun on Apr 24 2023, 1:48 PM.
Referenced Files
Unknown Object (File)
Sun, Apr 7, 1:09 PM
Unknown Object (File)
Thu, Mar 28, 7:41 PM
Unknown Object (File)
Thu, Mar 28, 7:38 PM
Unknown Object (File)
Mar 12 2024, 7:20 PM
Unknown Object (File)
Mar 7 2024, 7:48 AM
Unknown Object (File)
Mar 7 2024, 5:21 AM
Unknown Object (File)
Mar 6 2024, 11:41 PM
Unknown Object (File)
Feb 11 2024, 1:46 AM



basically copied the old RPC implementation

Depends on D7553

Test Plan

called the RPC with bloomRPC with an existing valid token, existing invalid token, and nonexistent token

Diff Detail

rCOMM Comm
Lint Not Applicable
Tests Not Applicable

Event Timeline

varun requested review of this revision.Apr 24 2023, 2:07 PM
jon added inline comments.
638 ↗(On Diff #25625)

I know this was named to fit the protobuf message format, but generally I feel that boolean values should be named something to indicate it is a boolean value, such as isXXX or hasXXX.

With token_valid, I'm not sure if this is "contents of a valid token" or "if the token is valid"

This revision is now accepted and ready to land.Apr 24 2023, 3:21 PM
This revision was automatically updated to reflect the committed changes.