microsoft / microsoft/PowerPlatformConnectors
Need help on Issue with OAuth Routing in Custom Power Automate Connector
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
We are building a custom Power Automate connector for HighQ with requirements to prompt for:
Client ID
Secret Key
Host URL
Auth URL
However, when implementing the OAuth flow using scripts/custom code, the routing does not work as expected. Instead of using the Client ID and Host URL, it redirects directly to the Host URL.
While reviewing GitHub, we found your connector to be very similar to our requirements. The Microsoft team mentioned they cannot assist with custom code.
Request:
Could you guide us with any documentation, references, or best practices? Even a high-level overview would be helpful. Also, are there any specific tools or approaches you recommend for handling this scenario?
Thanks in advance!
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
The issue mentions a custom Power Automate connector, OAuth flow, Client ID, Secret Key, Host URL, and Auth URL, but names no repository files, tests, or entry points. Start by identifying the connector definition and its OAuth routing configuration; done would require a concrete documented fix or reference explaining the redirect behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, cloud
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100