The get "my" subscriptions endpoint needs to find subscriptions based on the created by value

[SandGrainOne]

Description

The endpoint producing a list of registered subscriptions for a party/user of the API should use the CreatedBy field to do subscription retrieval. It's currently using the Consumer field.

The current implementation is working because in all scenarios the CreatedBy and Consumer fields have the same value. It's also impossible to set the Consumer field to anything different.

If we at any time make it possible for one party to create subscriptions for someone else it will be important that it is the creator of the subscriptions that can list out the subscriptions they've created.

Additional Information

Scenarios:
User_1 creates a subscription with a separate User_2 as consumer:

Filtering on Consumer (current implementation):

• User_1 loose access to the subscription after creating it. User_1 is unable to see the result of the subscription creation and the validation flag.
• User_2 has a new subscription suddenly appear in their list of subscriptions.

Filtering on CreatedBy:

• User_1 can see the active subscription and the result of the validation.
• User_2 can not easily see why events are being pushed. Here I would like to add that I'm not sure if User_1 will be able to register a subscription with an endpoint for User_2 without the knowledge of User_2.

Tasks

No response

Acceptance Criterias

No response

[olebhansen]

@SandGrainOne: Is this still relevant (or even possible), ref. discussing and closing #239?

[SandGrainOne]

@olebhansen Still relevant and possible. Unrelated to linked issue. Authorization of the events being hit by the subscription is separate from the subscription itself. Authorization of resource filter in the subscription must still be done based on the event consumer and not the subscription creator.

We currently do not support creating a subscription on behalf of a separate consumer, which is why this change is less important than it would otherwise have been. For me, the current implementation is a logical flaw, but because of the identical creator and consumer the functional outcome is unchanged.