Enable Providers and Consumers to Configure and Deploy Purchased Applications with the Offer Management Role

# Overview

We have the problem that customers with only the “App Service Provider Role” can create a technical user with the Offer Management role to use the DSI Onboarding UI.

A customer has purchased an application from an App Provider and would like to run it in their own cloud. In order to publish and deploy their app, and configure it with the portal, they require the same role as an App Provider—specifically, the Offer Management role (We can also have separate role named specifically for this use case, this needs to be decided).

## Explain the topic in 2 sentences
Customers with the “App Service Provider Role” can create a technical user with the “Offer Management” role. Additionally, customers (Providers and Consumers) who purchase an application and want to run it in their own cloud require the Offer Management role to configure and deploy their app.

## What's the benefit?
This change will allow customers to run their own applications in their own cloud and configure them independently using the Offer Management role.

## What are the Risks/Dependencies?
No major risk, as both Providers and Consumers will ultimately have the option to create a technical user with the “Offer Management” role. However, this change should be reviewed to ensure no unintended restrictions occur.

## Detailed explanation
Customers with the “App Service Provider Role” can create a technical user with the Offer Management role, which grants access to functionalities such as registering new connectors. However, this role should only be assigned under specific conditions.

Additionally, customers who purchase an application and want to deploy it in their own cloud need the Offer Management role to configure and manage the app within the portal. This is particularly relevant for companies that require control over their infrastructure and deployment.

### Current implementation
- Users with only the “App Service Provider Role” can create a technical user with the Offer Management role.
- Customers who purchase applications from App Providers do not have the required Offer Management role to configure and deploy their applications in their own cloud.

### Proposed improvements
- Allow customers (Providers and Consumers) who purchase an application to obtain the Offer Management role so they can deploy and configure their application in their own cloud.

## Feature Team

### Contributor
- @arnabcx

### Committer
- @typecastcloud

## User Stories
- Issue 1, linked to specific repository
- Issue 2, linked to another specific repository

## Acceptance Criteria
- [ ] Customers (Providers and Consumers) who purchase an application can obtain the “Offer Management” role to configure and deploy their app in their own cloud.
- [ ] The role assignment changes do not affect unrelated functionalities.

## Test Cases

### Test Case 1
#### Steps
2. Attempt to register a new connector as a customer who purchased an application but does not have the “Offer Management” role.
3. Verify that role assignment is correct after the update.

#### Expected Result
2. Customers who purchase an application should be able to obtain the “Offer Management” role and register new connectors.
3. No unintended access changes should occur.

## Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards [126](https://catenax-ev.github.io/docs/standards/CX-0126-IndustryCorePartType) and [127](https://catenax-ev.github.io/docs/standards/CX-0127-IndustryCorePartInstance), typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

- [ ] This feature aligns with our current architectural guidelines
- **Data Sovereignty:** All data sharing activities across company boundaries follow the [Catena-X Regulatory Framework](https://catenax-ev.github.io/docs/next/regulatory-framework/governance-framework), in particular the [Data Exchange Governance](https://catenax-ev.github.io/docs/next/regulatory-framework/20000ft/data-exchange-governance), and the [Dataspace Protocol](https://docs.internationaldataspaces.org/dataspace-protocol/overview/readme) via a compliant Connector (like the [tractusx-edc](https://github.com/eclipse-tractusx/tractusx-edc) or similar, see [Connector KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/connector-kit))
- [ ] [CX-0010 Business Partner Number](https://catenax-ev.github.io/docs/next/standards/CX-0010-BusinessPartnerNumber)
- [ ] [CX-0013 Identity of Member Companies](https://catenax-ev.github.io/docs/next/standards/CX-0013-IdentityOfMemberCompanies)
- [ ] [CX-0018 Data Space Connectivity (EDC)](https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity)
- [ ] [CX-0049 DID Document Schema](https://catenax-ev.github.io/docs/next/standards/CX-0049-DIDDocumentSchema)
- [ ] [CX-0050 Framework Agreement Credential](https://catenax-ev.github.io/docs/next/standards/CX-0050-FrameworkAgreementCredential)
- [ ] [CX-0149 Verified Company Identity](https://catenax-ev.github.io/docs/next/standards/CX-0149-Dataspaceidentityandidentification)
- **Interoperability:** Digital Twins are used (compliant to the [Digital Twin KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/digital-twin-kit) and the [Industry Core KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/industry-core-kit))
- [ ] [CX-0001 EDC Discovery API](https://catenax-ev.github.io/docs/next/standards/CX-0001-EDCDiscoveryAPI)
- [ ] [CX-0002 Digital Twins in Catena-X](https://catenax-ev.github.io/docs/next/standards/CX-0002-DigitalTwinsInCatenaX)
- [ ] [CX-0018 Data Space Connectivity (EDC)](https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity)
- [ ] [CX-0126 Industry Core: Part Type 2.0.0](https://catenax-ev.github.io/docs/standards/CX-0126-IndustryCorePartType)
- [ ] [CX-0127 Industry Core: Part Instance 2.0.0](https://catenax-ev.github.io/docs/standards/CX-0127-IndustryCorePartInstance)
- **Data Format:**
- [ ] The data model is based on a [published Semantic Model](https://github.com/eclipse-tractusx/sldt-semantic-models)
- [ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the [overarching architecture](https://eclipse-tractusx.github.io/docs/tutorials/e2e/inform/architecture)
- [ ] Potential risks or conflicts with existing architecture have been assessed

**Justification:** _(Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)_

## Additional information
- [ ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer).