microsoft / microsoft/PowerPlatformConnectors
[BUG] redirect_uri doesn't match the client registered redirect_uri
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Independent Publisher Connector
Name of Connector
Power Automate - HubSpot CRM - Create a contact
Describe the bug
After adding the "HubSpot CRM - Create a contact" connector from power automate, then being redirected via pop up window to MSFT I authenticate sucessfully. Then after sucesfull authentication I get an error saying
"Couldn’t complete the connection
The redirect_uri doesn't match the client registered redirect_uri. Please contact the app developer."
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 2 - One or more important connector features are down
To Reproduce
- add the "HubSpot CRM - Create a contact" connector in power automate
- authenticate via pop up to HubSpot
- Error appears after successful authentication
Expected behavior
After successful authentication, the redirect should be redirected to a page that confirms successful log in and the connector in power automate is activated
Environment summary
Install Method - Choosing the connector via power automate
CLI version NA
OS version NA
Shell Type NA
Additional context
NA
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the HubSpot CRM - Create a contact authentication flow in Power Automate and inspect the connector's OAuth redirect configuration. Compare the redirect URI used after authentication with the client-registered URI; done means authentication completes and the connector is activated without the mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100