sig#796: Connector registration fails if clearinghouseConnectDisabled gets disabled after onboarding

[evegufy]

Current Behavior

Company got onboarded with clearinghouseConnectDisabled enabled(feature eclipse-tractusx/sig-release#796), afterwards clearinghouseConnectDisabled got disabled again, which leads to the following Unexpected condition at connector registration for this company:

{
    "type": "https://datatracker.ietf.org/doc/html/rfc7231#section-6.6.1",
    "title": "The server encountered an unexpected condition.",
    "status": 500,
    "errors": {
        "Org.Eclipse.TractusX.Portal.Backend.Administration.Service": [
            "provider company 4f13981d-580d-4e9c-afae-d02ae70a775e has no self description document"
        ]
    },
    "errorId": "71c89c4a-6ce2-4d12-b4cd-998e0678f30b",
    "details": [
        {
            "errorCode": "CONNECTOR_UNEXPECTED_NO_DESCRIPTION",
            "type": "AdministrationConnectorErrors",
            "message": "provider company {companyId} has no self description document",
            "parameters": [
                {
                    "name": "companyId",
                    "value": "4f13981d-580d-4e9c-afae-d02ae70a775e"
                }
            ]
        }
    ]
}

Expected Behavior

Registration of connector is successful and this case is covered concept-wise at eclipse-tractusx/sig-release#796

Steps To Reproduce

Detected in v2.1.0

[evegufy]

@Phil91 I tested #894 and I still get the same error message as in the issue description but with a different error code:

{
    "type": "[https://tools.ietf.org/html/rfc7231#section-6.5.8"](https://tools.ietf.org/html/rfc7231#section-6.5.8%22),
    "title": "The resorce is in conflict with the current request.",
    "status": 409,
    "errors": {
        "Org.Eclipse.TractusX.Portal.Backend.Administration.Service": [
            "provider company null has no self description document"
        ]
    },
    "errorId": "6061c7d5-5ea3-4eba-baaf-1754cfa3e7eb",
    "details": [
        {
            "errorCode": "CONNECTOR_CONFLICT_NO_DESCRIPTION",
            "type": "AdministrationConnectorErrors",
            "message": "provider company {CompanyId} has no self description document",
            "parameters": [
                {
                    "name": "companyId",
                    "value": "4f13981d-580d-4e9c-afae-d02ae70a775e"
                }
            ]
        }
    ]
}

[Phil91]

@evegufy in my opinion the error is correct since the admin would need to trigger the selfDescription creation for the companies that don't have the selfDescription set. but let's discuss this with @MaximilianHauer

[MaximilianHauer]

as discussed the behavior is expected and wanted.
we should not provide workarounds for the whole process after the onboarding. goal of the trigger was only to support a smooth procedure during the onboarding.

• enable the user to finish the registration process
• ensure that the sd documentation is retriggered to enable further functionality for the user