microsoft / microsoft/PowerPlatformConnectors
Partner Centre Certification Process
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Hello Team
We are following the new process however there are a few issues we cannot circumvent:
- We cannot add our connector to a Power Automate solution to verify using the solution checker due to the following error: The request failed with error: '{"error":{"code":"0x80044331","message":"A validation error occurred. The length of the 'openapidefinition' attribute of the 'connector' entity exceeded the maximum allowed length of '500000'."}}'.
- We cannot use paconn either as it is generating the following error upon validation:
HTTPSConnectionPool(host='api.powerapps.com', port=443): Max retries exceeded with url: /providers/Microsoft.PowerApps/objectIds/71b6b311-8a5e-4e52-88c6-07e0e1301290/validateApiSwagger?api-version=2016-11-01&enableConnectorCertificationRules=true (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:2384)'))) - We cannot use paconn download, as after selecting the environment the following error occurs:
{
"error": {
"code": "InvalidAuthenticationToken",
"message": "The received access token has been obtained from wrong audience or resource."
}
}
401 Client Error: Unauthorized for url: https://api.powerapps.com/providers/Microsoft.PowerApps/apis?api-version=2016-11-01&%24filter=environment****redacted****
Can you advise please?
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 with the three failure reports in the issue: the Power Automate solution checker limit, paconn validation SSL error, and paconn download authentication error. Reproduce the affected certification steps if possible, then document a verified resolution or the precise external blocker for each failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100