Amendment to Application Identification

[Pavan-SAP]

Previous Approach

Previously, we identified applications using the provider's globalAccountId and btpAppName. However, this approach had a critical limitation: the globalAccountId in the subscription payload might not belong to the provider, making it impossible to uniquely and reliably identify applications.

Target Solution

We have introduced providerSubaccountId to the CAPApplication specification to address this issue. This identifier is included in the subscription payload (e.g. for saas-registry) and, when combined with btpAppName, provides a unique and accurate way to identify applications.

Migration Plan

We plan to deprecate globalAccountId and replace it with providerSubaccountId in the CAPApplication specification in the upcoming release. We recommend updating your configurations to use providerSubaccountId already now (available since 0.24.0) to ensure compatibility.