-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Current Behavior
As an app provider, in the Catena-X INT environment, we are testing the unsubscribe and re-subscription flow for our application.
We had previously configured and successfully subscribed the “Connect & Integrate” app (offerId: ce71a1c5-f622-49d5-9e3b-75b1cc5944e3, subscriptionId: b121c4b6-fe42-4a77-9e2e-a52126a6a7a4).
To test the unsubscribe behavior:
We used the Company Subscription → Unsubscribe option for the “Connect & Integrate” app.
The subscription status transitioned from Active to Declined and Inactive as expected but that app still visible in Business Apps.
Later, we initiated a re-subscription from the App Marketplace:
The re-subscription request was submitted and processed successfully.
As the app provider, we received a trigger request from the Catena-X portal backend.
However, when attempting to configure the offer subscription by calling the /start-autoSetup API with the subscription requestId, the request failed with a 409 Conflict error.
API Request
Endpoint: POST /start-autoSetup
Request Body:
{
"requestId": "192a59c8-b02a-4922-8511-0dce8ed70a69",
"offerUrl": "https://mehran-192a59c8.dih.com"
}
Error Response:
{
"type": "https://tools.ietf.org/html/rfc7231#section-6.5.8",
"title": "The resource is in conflict with the current request.",
"status": 409,
"errors": {
"Org.Eclipse.TractusX.Portal.Backend.Framework.Processes.Library": [
"offer subscription 192a59c8-b02a-4922-8511-0dce8ed70a69, process step AWAIT_START_AUTOSETUP is not eligible to run"
]
},
"errorId": "21075d3a-70be-4798-afd4-c1bf92890e69",
"details": []
}
The subscription details and status at portal end as below
"offerId": "ce71a1c5-f622-49d5-9e3b-75b1cc5944e3",
"offerName": "Connect & Integrate",
Old subscription (this subscription used for unsubscribe )
{
"companyId": "d3f4e669-f164-47bd-9062-1d17b9ad7406",
"companyName": "Mehrans Eisdiele",
"subscriptionId": "b121c4b6-fe42-4a77-9e2e-a52126a6a7a4",
"offerSubscriptionStatus": "INACTIVE",
"country": "DE",
"bpnNumber": "BPNL000000000ISY",
"email": "Sachin.Argade@t-systems.com",
"technicalUser": true,
"processStepTypeId": null
}
New subscription
{
"companyId": "d3f4e669-f164-47bd-9062-1d17b9ad7406",
"companyName": "Mehrans Eisdiele",
"subscriptionId": "192a59c8-b02a-4922-8511-0dce8ed70a69",
"offerSubscriptionStatus": "PENDING",
"country": "DE",
"bpnNumber": "BPNL000000000ISY",
"email": "Sachin.Argade@t-systems.com",
"technicalUser": true,
"processStepTypeId": "RETRIGGER_PROVIDER"
}
Expected Behavior
As the app provider, once we receive the trigger from the Catena-X portal backend during re-subscription, we should be able to:
- Successfully call the /start-autoSetup API with the new offer subscription requestId.
- Configure the offer subscription URL.
- Receive a new technical user if the app requires one and is configured accordingly (e.g., multiple user profiles linked to the app).
- This process should work even in a re-subscription scenario, after the original subscription was previously marked as declined or reset.
Steps To Reproduce
- Release an app in the App Marketplace
- Ensure the app is approved and available
- Subscribe to the app → observe successful configuration and activation
- Go to Company Subscription and click Unsubscribe
- Re-subscribe to the app from the marketplace
- As app provider, handle /start-autoSetup request → observe failure (409 Conflict)
Metadata
Metadata
Assignees
Labels
Type
Projects
Status