Consider Correct Subscriber in Application Sharing Scenarios

[hisanhunais]

Problem

When application sharing is enabled, in several scenarios the application creator is taken as the subscriber and not the actual subscriber.

One such scenario is during the subscription deletion workflow, although a subscription of a shared application is deleted by a user who is not the application owner, the application owner is displayed as the Subscriber in the Admin portal.

In the current design, when an application is created, an entry is added to the AM_APPLICATION table where the application creator is added as the subscriber. When deleting a subscription, the subscription details are fetched and this subscriber is taken from the AM_APPLICATION table. This subscriber (application creator) value is the detail which gets added as the Workflow entry and gets displayed in the Admin portal.

Solution

Introduce a way to keep track of the subscriber in application sharing scenarios

Affected Component

APIM

Version

No response

Implementation

No response

Related Issues

No response

Suggested Labels

No response