Connector Config Details - missing error handling on API call /companyData/decentralidentity/urls

[jjeroch]

Detected in version: 2.0.0 RC4

Related Tickets: Follow up ticket of #674 & #643 & #683

Description: The connector configuration frontend element/implementation does not handle API errors properly, resulting in a poor user experience. We need to make adjustments to the frontend section to handle API errors gracefully and ensure that customers are informed about any errors that occur.

The current lack of error handling in the frontend can lead to confusion and frustration for customers. Without proper notification of API errors, customers may not be aware of issues and may continue to interact with the application without realizing that their actions were unsuccessful. This can result in data inconsistencies and a poor user experience.

Page: /technicalsetup Function: Connector Configuration

Expected Behavior: When an API error occurs (401, 403, 409, 500, etc...), the frontend should handle it appropriately and inform the customer about the error. This can be achieved by displaying an error message or notification on the UI, providing clear and concise information about the error.

[manojava-gk]

Error component with try again is for 500 status code.