Our use case is to relax validation rules in cases where the update is made from an external system.

Each user authenticates individually so unfortunately we cannot look for an API user.

  • You'll need to create and propagate context to distinguish between user-coming-from-external system versus user-coming-from-wherever-else. Since wherever-else is very broad and undefined in your question, this becomes an open-ended question that is frowned upon around here. The answer in possible duplicate above is one potential option where "wherever-else" is a UI-based update. – identigral Oct 21 '19 at 16:42
  • Thanks but I don't see how the other question relates to updates performed by the REST API? – James Graham Oct 29 '19 at 8:19

Browse other questions tagged or ask your own question.