Open severinbeauvais opened 2 years ago
Time-box research on this ticket: After we complete the time-boxed research, we are going to revisit this and re-estimate.
@lmcclung @davemck513 is this intended to be open. It's labelled as a P1 spike. If this closes the epic may be closed. If this is being pushed perhaps we take this out of the epic and close the epic?
The risk of not doing this is that a user could access or update an entity while using the wrong account.
Example:
The issue in step 7 will be resolved in #10880.
The issue in step 8 is the subject of THIS ticket. When a call is made to the Legal API, the authentication/authorization step should validate the account ID -- the wrong account should not be able to access an entity's data (even though it's the same user in both cases).
I am not sure about the priority of this ticket. On the one hand, it should only happen when a user enters the URL manually (or restores a bookmark). Also, this issue has existed for some time. On the other hand, it may be serious that the wrong account is used to modify an entity...?
cc: @shabeeb-aot