Page MenuHomePhabricator

[identity] verify user access token
ClosedPublic

Authored by varun on Apr 24 2023, 1:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 24, 3:31 AM
Unknown Object (File)
Tue, Dec 24, 3:31 AM
Unknown Object (File)
Tue, Dec 24, 3:31 AM
Unknown Object (File)
Tue, Dec 24, 3:29 AM
Unknown Object (File)
Fri, Dec 20, 1:55 AM
Unknown Object (File)
Oct 27 2024, 12:19 AM
Unknown Object (File)
Oct 10 2024, 1:12 PM
Unknown Object (File)
Oct 1 2024, 1:02 PM
Subscribers

Details

Summary

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

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

varun requested review of this revision.Apr 24 2023, 2:07 PM
jon added inline comments.
services/identity/src/client_service.rs
638

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.