Page MenuHomePhabricator

In Phortune, use actual merchant authority (not authority grants) to control account visibility
ClosedPublic

Authored by epriestley on Aug 16 2019, 3:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 17, 12:19 AM
Unknown Object (File)
Fri, Oct 25, 8:27 PM
Unknown Object (File)
Oct 24 2024, 10:17 AM
Unknown Object (File)
Oct 20 2024, 4:37 AM
Unknown Object (File)
Oct 19 2024, 6:23 AM
Unknown Object (File)
Oct 11 2024, 6:01 PM
Unknown Object (File)
Oct 9 2024, 12:35 PM
Unknown Object (File)
Oct 2 2024, 3:43 AM
Subscribers
None

Details

Summary

Depends on D20715. Ref T13366. See that task for discussion.

Replace the unreliable "grantAuthority()"-based check with an actual "can the viewer edit any merchant this account has a relationship with?" check.

This makes these objects easier to use from a policy perspective and makes it so that the Query alone can fully enforce permissions properly with no setup, so general infrastructure (like handles and transactions) works properly with Phortune objects.

Test Plan

Viewed merchants and accounts as users with no authority, direct authority on the account, and indirect authority via a merchant relationship.

Diff Detail

Repository
rP Phabricator
Branch
merchant5
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 23257
Build 31949: Run Core Tests
Build 31948: arc lint + arc unit