Page MenuHomePhabricator

Allow "MFA Required" objects to be edited without MFA if the edit is only creating inverse edges
ClosedPublic

Authored by epriestley on Dec 18 2018, 4:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 21, 11:55 AM
Unknown Object (File)
Thu, Mar 21, 11:55 AM
Unknown Object (File)
Thu, Mar 21, 11:55 AM
Unknown Object (File)
Thu, Mar 21, 11:55 AM
Unknown Object (File)
Sun, Mar 17, 12:30 PM
Unknown Object (File)
Sun, Mar 17, 2:48 AM
Unknown Object (File)
Tue, Mar 5, 7:26 AM
Unknown Object (File)
Feb 12 2024, 10:16 PM
Subscribers
None

Details

Summary

Depends on D19900. Ref T13222. See PHI873. When an object requires MFA, we currently require MFA for every transaction.

This includes some ambiguous cases like "unsubscribe", but also includes "mention", which seems like clearly bad behavior.

Allow an "MFA" object to be the target of mentions, "edit child tasks", etc.

Test Plan
  • Mentioned an MFA object elsewhere (no MFA prompt).
  • Made an MFA object a subtask of a non-MFA object (no MFA prompt).
  • Tried to edit an MFA object normally (still got an MFA prompt).

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable