[BUG] Square Payments is unable to authorize

Type of Connector

Independent Publisher Connector

Name of Connector

Square Payments

Describe the bug

I created a Logic App workflow and added in a Square Payments action. When I attempt to authorize myself, I'm met with the following error:

Here is the full url:

https://squareupsandbox.com/oauth2/authorize?client_id=sq0idp-bjhfropQ5DM7gobOrHkHUA&response_type=code&redirect_uri=https%3a%2f%2fglobal.consent.azure-apim.net%2fredirect&scope=&state=459f5c37-c7bc-4cf4-b5ae-430ba31c4514_logic-apis-westus2_azure-apim.net

You'll notice that it is also pointed at the sandbox URL.

For what its worth, I did try using the production URL and replacing the Client ID with my own, but I was still met with an error:

Failed with error: 'OAuth2 authorization flow failed for service 'Generic Oauth 2'. OAuth 2 sign in failed to exchange code for access token. Client ID and secret sent in form body.. Response status code=Unauthorized. Response body: { "message": "Not Authorized", "type": "service.not_authorized" } Client ID and secret sent in Basic authorization header.. Response status code=BadRequest. Response body: { "message": "missing required parameter 'client_id'", "type": "bad_request.missing_parameter" } '. Please sign in again.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

This is very simple to reproduce (at least in a Logic App):

1. Create a workflow
2. Add a Square Payments action (and don't already have an existing connection)
3. Click on the Sign In button in that new action.

Expected behavior

I would expect to be presented with a Square login screen and then be able to sign into my Square account and be able to use the connector.

Environment summary

Azure Logic Apps

Additional context

I'll tag @troystaylor since he is the author of this connector.

Thanks!

Start by reproducing the Square Payments authorization flow in Azure Logic Apps using the steps and authorization URL in the report. Inspect the Square Payments connector's OAuth configuration and compare its sandbox and production behavior; done means a Square login completes and the connector can create a usable connection.