[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 commented 9 months ago

Does this bug already exist in our backlog?

[X] 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'.'

powerpaltform-coe-get-connectors-error_synctemplatev3-customconnectors_240212

powerpaltform-coe-get-connectors-error_cleanuphelper-checkdeletedcustomconnectors_240212

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 commented 9 months ago

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

Jenefer-Monroe commented 9 months ago

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.

heatheronder commented 9 months ago

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

OctavianSfetcu commented 9 months ago

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

OctavianSfetcu commented 9 months ago

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

Jenefer-Monroe commented 9 months ago

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.

heatheronder commented 9 months ago

@Jenefer-Monroe The change you mentioned is for security when configuring custom connectors, correct? I don't understand why this would impact the ability to retrieve the custom connectors from our tenant using a standard action/connector that Microsoft provides. I have a meeting with an engineer at 4pm CST today and will post an update with how that goes.

Jenefer-Monroe commented 9 months ago

I think it’s related due to timing and the similarity of the error message here and in be ux. I could be wrong though. Please let us know what you find in your investigations

VanIsleCA commented 9 months ago

Same issue in Canada.. I will open a ticket with Microsoft. Please let us know with any updates. Thanks,

VanIsleCA commented 9 months ago

Also, looks like there's been a similar issue reported here, back in 2023. Microsoft has fixed it then and pushed the update. Link here: https://github.com/microsoft/coe-starter-kit/issues/5580.

Chitusnair commented 9 months ago

Same issue in Austria. Look forward to getting any updates on this.

uka-support commented 9 months ago

same here (Germany) - issue first popped up two days ago (2024-02-13 03:03 UTC), last seen this night (around 04:11 UTC).

Only "Admin | Sync Template v3 (Custom Connectors)" affected here (maybe because nobody deleted flows yet)

MartinWGT commented 9 months ago

Same here (UK) started today.

dtrandall commented 9 months ago

Same here US started trouble today

gregvolz commented 9 months ago

Working with a customer and they just installed January a few weeks ago (fresh install in a test tenant) so no custom connectors. Tried running the upgrade today and received the error reported above. I'll have them spin up a new environment and try a fresh install (I know this won't help anyone doing an upgrade).

Jenefer-Monroe commented 9 months ago

I hear you that this is surfacing in the kit and that is frustrating, but this is an out of the box connector and so this call failing is something that the product team will need to resolve. Please contact product support.

Jenefer-Monroe commented 9 months ago

assigning back to Grant so he can drive there from our side, but customer reports are really the best way to initiate chane.

Grant-Archibald-MS commented 9 months ago

Thanks @Jenefer-Monroe following up with connector team

uka-support commented 9 months ago

We do not use any custom connectors and the error pops up in like all our environments (including the default environment)

We are on 4.22 (recently upgraded in January from December version)

Michaelbubbles commented 9 months ago

Hi, Is PowerCat Team working on a fix? Seems like this issue is regarding everyone.

From Norway/EU.

nilsnutz commented 9 months ago

We are also receiving this error. We found out that the issue also appears if you manually try to use the "Get Connectors" Power Apps for Maker action in a flow.

SteveBaillargeon commented 9 months ago

I'm in CA, and same here: Only "Admin | Sync Template v3 (Custom Connectors)" affected Is this going to be taken by CAT Team support or we have to open a ticket to MS ?

Chitusnair commented 9 months ago

I have issue with the "Admin | Sync Template v3 (Connectors)". The The Admin | Sync Template v3 (Custom Connectors) for me is still turned off. I assume I will get the same error there as well. I raised a ticket with Microsoft, the first level collected the details and hopefully assign to the right team. Keen to get this resolved.

jackpoz commented 9 months ago

Is Microsoft going to fix the connector on their side for all tenants and environments or do they expect every single affected tenant to open a support ticket ?

Jenefer-Monroe commented 9 months ago

Hello Power Cat is pressing for a fix here but cannot fix it ourselves.

You creating support tickets helps us press for the fix more quickly but you don’t have to if it’s difficult for you. I totally understand

santiareh commented 9 months ago

Following the issue, I'm experiencing the same thing and the Admin | Sync Template v4 (Custom Connectors) flow too.

Thanks Power CAT team for pressing on this issue for us.

Grant-Archibald-MS commented 9 months ago

As a status update. We have connected with the internal team who have replicated the issue, assessment is still ongoing

gregvolz commented 9 months ago

[like] Greg Volz reacted to your message:

From: Grant Archibald @.> Sent: Friday, February 16, 2024 10:00:39 PM To: microsoft/coe-starter-kit @.> Cc: Comment @.***> Subject: Re: [microsoft/coe-starter-kit] [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 pr...

As a status update. We have connected with the internal team who have replicated the issue, assessment is still ongoing

— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/coe-starter-kit/issues/7630#issuecomment-1949395628 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUP4JEF6M6MGB2AWAMBLBFDYT7JIRBFKMF2HI4TJMJ2XIZLTS2BKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDSNRSGIZDCMRWGGSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRTGAYTSNRZHEZTKONENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWVDKOJTGM3DGNBQGQ42I3TBNVS2S2DBONPWYYLCMVWKY43VMJVGKY3UL52HS4DFVREXG43VMVBW63LNMVXHJJTUN5YGSY3TSWBKI5DZOBS2U4TFOBXXG2LUN5ZHTJLWMFWHKZNJGI4TKMZYHA2TKNMCUR2HS4DFUVUXG43VMWSXMYLMOVS2UMRRGI4TQNJQGMZTJAVEOR4XAZNFNRQWEZLMUV3GC3DVMWVDEOJWGIZDEMJSGYYYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTAMJZGY4TSMZVHGBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGU4TGMZWGM2DANBZU52HE2LHM5SXFJTDOJSWC5DF. You are receiving this email because you commented on the thread.

Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Grant-Archibald-MS commented 9 months ago

Status update: Internal team is working on the issue

sharmajitendralal commented 9 months ago

I have same issue with the "Admin | Sync Template v3 (Connectors)".

madhavjaya commented 9 months ago

What is the status on this issue please. I have few COE toolkit implementation engagements with the customers and I would really like to get this fixed asap. What is the turnaround time to fix this issue?