You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure, if it's only backend or only frontend. Thus I placed it here.
Current Behavior
I got two partners on association INT:
Control Unit Creator Incorp.
Semiconductor Supplier Incorp.
Control Unit Creator Incorp. acts as Application Provider for both companies for one app.
I deployed the connectors accordingly and did the following incorrectly:
Added managed connector registration for Control Unit Creator Incorp for supplier-edc's url
Recognized it's wrong, but didn't first delete the wrong configuration
Added managed connector registration for Semiconductor Supplier Incorp for supplier-edc's url
Only one managed connector is shown and CAN NOT be deleted.
Expected Behavior
Two managed connectors are shown and can be deleted OR registration doesn't pass if url is already in use for another BPNL
Steps To Reproduce
Subscribe two companies to one company's application
As application provider: register managed connectors incorectly
subscription of partner A with address of partner B
subscription of partner B with address of partner B
-> problem: only one connector is registered, can't be deleted and no other connector may be registered for subscription.
The text was updated successfully, but these errors were encountered:
Not sure, if it's only backend or only frontend. Thus I placed it here.
Current Behavior
I got two partners on association INT:
Control Unit Creator Incorp. acts as Application Provider for both companies for one app.
I deployed the connectors accordingly and did the following incorrectly:
Only one managed connector is shown and CAN NOT be deleted.
Expected Behavior
Two managed connectors are shown and can be deleted OR registration doesn't pass if url is already in use for another BPNL
Steps To Reproduce
-> problem: only one connector is registered, can't be deleted and no other connector may be registered for subscription.
The text was updated successfully, but these errors were encountered: