[CoE Starter Kit - BUG] The API 'powerappsforappmakers' returned an invalid response for workflow operation 'Get_Connectors' of type 'OpenApiConnection'. Error details: 'The API operation 'Get-Connectors' requires the property 'body/value/776/properties/connectionParameters/username/uiDefinition/constraints/required' to be of type 'String' but is of type 'Boolean'.'

[ramontebar]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

This bug is related to 5580 and 7251

This error is affecting two flows:

• Admin | Sync Template v3 (Custom Connectors)
• CLEANUP HELPER - Check Deleted (Custom Connectors)

We have noticed the affected environments are Developer and Teams environments in Asia.

Error details:
The API 'powerappsforappmakers' returned an invalid response for workflow operation 'Get_Connectors' of type 'OpenApiConnection'. Error details: 'The API operation 'Get-Connectors' requires the property 'body/value/776/properties/connectionParameters/username/uiDefinition/constraints/required' to be of type 'String' but is of type 'Boolean'.'

Expected Behavior

Get connectors for the environment within the filter query

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.22

What app or flow are you having the issue with?

Admin | Sync Template v3 (Custom Connectors) and CLEANUP HELPER - Check Deleted (Custom Connectors)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[bradyoung1]

We are having the same issue on Preview (US) region. All other regions are not having the issue.

[Jenefer-Monroe]

Hello. Thanks for posting, unfortunately this in an issue with the what the product is returning via the connector and not with the kit. I just went to an environment like this and see it repro in the UX as well.
I suggest you create a support ticket. I will try to press internally as well.

[hlo-olh]

I am also seeing this error for one environment. I will open a case with Microsoft.

[OctavianSfetcu]

Hi
we have the same issue in Switzerland, with the same CoE Kit 4.22. Environments with or without Dataverse.

[OctavianSfetcu]

I've opened a Ticket to MS yesterday, but nothing new so far. Does anyone have any news regarding this? Thx

[Jenefer-Monroe]

Evidently the following was in the message center yesterday. I have not tried out these steps yet myself but will. Please others here let us all know if you succeed.

Communication and action needed for customers (admins) below:

We have changed the way the Custom Connectors feature using OAuth 2.0 works in Microsoft Power Platform and Azure LogicApps. In addition to displaying an anti-phishing page for custom connectors that share a single redirect URI, we have rolled out a change where all newly created custom connectors will automatically have a per-connector redirect URI when selecting OAuth 2.0 as the authentication method. We have also deployed a change to allow you to modify existing custom connectors to use a per-connector redirect URI in the Custom Connector portal, under the Security tab.

What action do I need to take?
We recommend that you update your existing connectors that use OAuth 2.0 to authenticate to use a per-connector redirect URI to ensure the highest level of security and user experience.

• If you created your custom connectors with the web interface, edit your custom connectors, navigate to the “Security” tab, and check the box “Update to unique redirect URL,” and save to enable the per-connector URI.
• If you created your custom connectors with multi-auth using the command line interface (CLI) tool, you need to update your connector using the CLI tool to set "redirectMode": "GlobalPerConnector".
• Once the custom connectors have been updated to use the per-connector URI (either through the setting in the Security tab or using CLI tool), you should remove the global redirect URI from your oauth2 apps, and add the newly generated unique redirect URL to your OAuth 2.0 apps.
• We will also be enforcing this update for existing custom connectors starting February 16, 2024, and any custom connector that has not been updated to use a per-connector redirect URI will stop working for new connections and show an error message to the user.
  If you have any questions or feedback, please contact custom support, and reference ICM414775535.